I have a tall Dynamic Registration form with 5 repeating sections for entering children's names and details.
To make the form shorter, I have hidden the sections for child 2-5 using the "Hide until forced visible by question event" setting. And created question events to un-hide the child sections (a group of fields) one-at-a-time as needed.
I also created question events to hide these sections again if a collection of fields were revealed but were unneeded. So the user could hide them again.
That is all good. And when the user saves the data, and leaves the form and returns to it, it shows his data as it was stored. Also good.
But if the family has 3 children and the form opens on a return visit showing only the first one, the user will click to un-hide the other two children and find that the stored data for child 2 and 3 is not visible.
They wonder where the data for the other two children has gone. I know it is still in the database. But it does not populate the form. They wind up re-entering the children which is a bother for them and bad for the data when they enter the children out of order from the previous time. As DR will save the new data into the same record as the old which can effectively mix the children's data together.
Here is what I ask.
1. Can the form be smart enough to open with the right number of children sections visible for the family on a re-visit? And how?
2. OR if the user runs a question event to un-hide a hidden child section of fields, can the form re-populate the child's data into those revealed fields?
3. Or if I have to leave all the fields for all 5 children visible all the time, how can I still have field validation on the fields they don't use? It they try to save without entries for child 5, it won't let them.
Thanks for your suggestions.