If I can view all applicants in a list, then I don't need to find which application that the applicant is associated, can it be done from WP dashboard or I have to have a View to do?
Is it possible to allow me to update the applicant without finding its parent application if it is treated as a new post?
Hello. Thank you for contacting the Toolset support.
Do you mean that you want to display all applicant belongs to specific single post on single post page? If that is correct, to display the repeating field group entries, you will have to create a view.
Is it possible to allow me to update the applicant without finding its parent application if it is treated as a new post?
==>
I do not understand this, can you please share test case. Do you mean that you want to create a new entry for "applicant " without attaching the parent? if that is correct - no, repeating field groups entries are internally store as a child post type and parent will be the one from where you are creating the repeating field group entry.
If repeating field groups entries internally store as a child post type, how can I access them from the dashboard like child post?
What is the difference between creating a child post and creating a repeatable custom field? Do both look to make a post-relationship with a parent post?
No matter I create a new CTP or repeatable custom field, can I add the record using CRED the same way?
If repeating field groups entries internally store as a child post type, how can I access them from the dashboard like child post?
==>
The repeating field group entries access will be available one edit post page.
What is the difference between creating a child post and creating a repeatable custom field? Do both look to make a post-relationship with a parent post?
==>
The difference between repeating field group and one-2-many post relationship is when you use repeating field group the one-2-many post relation relationship is maintain internally automatically between the single post and repeating field group entries you create where as using post relationship you will have to create one-2-many post relationship between your desired post type explicitly.
Thanks for your explanation, other than the post-relationship is maintained internally, and custom make the relationship, any pros, and cons to different strategies?
The only difference is if I want to manage the applicant from the backend directly, I have to use child and parent post-relationship, any others?
As far as I can say not much but I would encourage you to have hands on experience of both. You can use our free test platform http://www.discover-wp.com and use any of our reference site that is build on top using Toolset and check what mode (repeating field group or post-relationship) suits best as per your requirement and then take next steps.
OK, I decided to use the post-relationship as I want to keep it simple to let the system administrator easily search the applicant from the backend and do the data update if need.
I have another question about the custom field condition, if you think it should be posted as a separate post, please do so.
Please refer to the attached screenshot, this is a sample of the relationship between application and applicant post, both have a common custom field Application Type, when I create a CRED form, how can I hide and show individual custom fields from the applicant when I change the Application Type from the parent post Application? I know how to set the condition in the custom field but how can I change the custom field Application Type in the Applicant post same as the Application Type in the Application post?
Best regards,
Kelvin.
New threads created by Minesh and linked to this one are listed below:
