This is a long one. Thank you in advance for any replies!
I’m wondering about the best way to currently accomplish a desired functionality, if it’s even possible at all, or if I might not be thinking of this correctly.
A client of mine conducts surveys to their users, and they internally want to to a view a particular survey, see those survey responses, and take actions (ex. communicate with the user) depending on any particular user’s survey response.
Each survey has a few common elements—say name and email—but the surveys differ in their questions, the number of questions, and their responses.
It’s clear to me how I would create the dynamic survey pages (via a collection page), but it’s not clear to me how I would create a dynamically structured table element or dynamically structured data grid element. Here’s an example of what I’m trying to accomplish (gigs = surveys).
I noticed I can only create these dynamic survey pages if I use a static collection (“for SEO purposes”. However, this will be an internal tool. Are the dynamic collection pages mainly for public-facing pages (similar to a la a CMS system)? Should I create the survey pages as regular pages and control which survey page the user is on via a variable?
It looks like the current method of creating a data grid relies on establishing a fixed structure upfront(screenshot directly below), which wouldn’t work with my use case. This wouldn’t work from me because the particular table I want to create should have a dynamic structure. Am I understanding this correctly?
If 3 is possible, would there be a way to make the table interactive to the extent that someone could do something like A) filter the table B) select a row of the table?
If interactivity described in 4 is not possible, could this be accomplished by creating a custom component following the developers’ documentation?
Am I over-complicating this by not structuring my database correctly? Here’s how I currently structure my database—
– Includes the survey’s attributes
– Includes the user’s attributes
- Survey Responses
– Includes survey as a field reference
– Includes user as a field reference
– Includes a JSON field to store the questions and response data for the particular survey