@jerneva.cowell you do not need to nest any RG
- Create an option set you call ‘answers’ (I say this assuming all questions will have the same set of 4 choices (ie: Yes, NO, Maybe, Sometimes)…and these four choices are your option set values.
- Create the card with a single RG that is your list of options.
NOW, if you want different answer choices for each question, again, absolutely no need to nest any RG. You can instead ensure your data type of ‘question’ has a field called ‘answer’ and that field is of type text or could be related to another data type (other data type only if your creation of answer choices is needing to be updated often or user created).
So let’s say you have a data type simply named ‘question’ and a field called ‘answer_choices’ you will have a group that is the container and that group will have a data source of ‘question’ and then your single RG inside of the group container will be of type ‘text’ and your source will be ‘parent groups questions’ answer_choices’…this allows you to have a group container with text for the question and rg for the answer choices and simple reference for saving the selected answers knowing which question it is for.
1 Like