Hi and thank you.
After watching this tutorial just now, I may have unearthed (partly) the problem.
By example:
- A user completes a survey Form containing various input component kinds. To mildly complicate things (but not by much), there are five (qty. 5) varieties of survey Forms. But whichever the variety, once the SUBMIT button is pressed, I need to capture component attribute content (i.e. what the survey taker inputted). Each variety will, of course, require different collection-code because their components differ. (Note: I’m not concerned that the code will differ. I don’t care).
I never need to write / update component attribute properties (ever). I only need to read them (i.e. what the user inputted). I thought Data Bindings would be helpful here, but I’m not so sure.
I’ll just programmatically determine the form kind and scrape component attribute content in code. It goes back to the title of this post: Capturing Form component attributes into a data structure.