Hi, I’m struggling to work through this. I think there is a really easy solution and I’m just too close to it to see it.
This example isn’t the exact thing I’m trying to do but it’s a simplified version so I don’t have 8 paragraphs of context.
Admin creates a ‘Course’. Each Course has multiple ‘Lessons’. Each lesson has a unique ‘checklist’, and list of ‘Response Blocks’.
There will be multiple different courses each with unique lessons, checklists, and response blocks of course.
Here’s the tricky part… at least in my head, is that users will be able to deploy more than 1 of the same course in their account, so they can go through it again with a fresh list of responses and unique checklists. Almost like if they were completing the course for different clients, or business ideas.
How would I go about structuring the data in a way that the user can have multiple instances of that 1 course made up of different connected data types?
Here’s the only way I can figure it out, but I’m not sure if its the best way.
It’s pretty easy to do by having a page for each type of course that uses groups or Reusable Elements to hide/show each lesson, and the content for each lesson is built into the page instead of it being displayed dynamically. Then I have a Data Type that only needs to store the Lesson as a boolean filed or y/n to track completions. Each checklist could be stored using a list of options in an option set. And the Response Blocks would be a list of Data Type Response Blocks.
This way, when a user wants to deploy another instance of a course, all I have to do is run a workflow that creates another ‘Course Type 2’ for example.
Here’s how that would look:
Is this the best way to move forward or is there something I’m missing?