" if the field "dtap-1st-dose" only exists in the DtAP RFG, then there's no need to include it in Hep-A RFG results. "
By having all RFGs selected in this View, am I understanding that these RFG groups will also display the field "dtap-1st-dose" data if there is data in this field?
If I go to the side-bar menu item "Immunizations - Add New" I can see the Field Groups and their respective fields. I'm still not clear how to display this form on a page for a user to enter immunization data. This is the form I added the form to the TS Support test page.
By having all RFGs selected in this View, am I understanding that these RFG groups will also display the field "dtap-1st-dose" data if there is data in this field?
Yes, that is correct. Anything you put in the loop will be shown for all RFGs regardless of the current RFG type in the loop (DtAP , HepA, etc.) You can use conditional HTML or other techniques to manage field display within the loop, or you can use separate Views for each RFG type.
If I go to the side-bar menu item "Immunizations - Add New" I can see the Field Groups and their respective fields. I'm still not clear how to display this form on a page for a user to enter immunization data. This is the form I added the form to the TS Support test page.
That's what I was trying to explain earlier, it's not currently possible to do everything like this in one Form. The experience will be:
- Create Immunization post in Form 1
- Create RFG type 1 (like DtAP) in Form 2
- Reload the page, create another RFG type 1 in Form 2
- Go to a different page, create RFG type 2 (like HepA) in Form 3
...and so on.
This screenshot is the one on the ticket assigned to Luo Yang, where I asked if you could take a look where I have requesting assistance for pretty much the same issue. Ultimately though, this is the format I want to output as a form for input by a parent - if possible with HTML in the View loop.
Otherwise, I'd like to have the form as close as possible available with the RFGs and respective dose/date fields available, as is the current setup of the Immunizations custom post type I setup. The ticket is here https://toolset.com/forums/topic/assistance-with-a-table/, and am wondering if you could take ownership of this ticket seeing that we've made some progress on the same issue. Just the tickets I created were assigned to other engineers, but mostly were related. Hopefully you can now see where my goal is headed.
My week is ending shortly but I will return on Sunday. If you would like to transfer that ticket to me, please let Luo know in that ticket and I will take it from his queue when I return.
At first glance it seems like you could have several groups of date fields on the immunization report post without the need for RFGs, which are overcomplicating things. Something like this:
Dtap Group
- Dtap 1st dose
- Dtap 2nd dose
- Dtap 3rd dose
- Dtap 4th dose
- Dtap 5th dose
HepA Group
- HepA 1st dose
- HepA 2nd dose
HepB Group
- HepB 1st dose
- HepB 2nd dose
- HepB 3rd dose
...and so on...
This would make it possible to collect all the data in one Form, without the need for multiple RFG forms. It has implications for search as well. For example, it's not currently possible to search or filter a View of Immunization Reports by Dtap 1st dose when that field is part of a RFG applied to the Immunization Report post type. It's possible if Dtap 1st dose is a field directly on the Immunizations Report post, though. As you noticed, you cannot have multiple fields with the slug 1st-dose, so you would have to make each field's slug unique.
I read through your comments in the other ticket and I'm not convinced the Immunizations Report post type is needed at all. It seems you should have all these fields directly on the Child post. Then you can do things like filter Children based on the date (or no date) of their dtap 1st dose.
Thanks Christian,
I can wait until you return, and thank you for this last reply. I'll send a message to Luo requesting to assign the ticket to you.
Have a good weekend.
Sure, I have picked up the other ticket and we can discuss more there.
