Hide or grey out choice if already chosen by a respondent
Good afternoon!
We have a survey that respondents can enter multiple times to select a person(s) they want to provide feedback for. The link is anonymous but we use an authenticator with a unique ID so we can track completion.
The respondent selects one or more people and are looped through a series of questions. The issue we’re trying to solve for is the next time they enter the survey to give feedback on someone else they still see the people they already provided feedback for. We’re trying to either hide, grey out, or make those options no longer visible for that respondent.
Does anyone have any ideas on how to do this?
Any help would be appreciated.
Thank you, Stephanie
Page 1 / 1
You can add that information to the XM directory via workflows task and then when they return use that information via embedded data along with the option level display logic to hide the choice.
@Deep thank you for the quick reply.
this is my teams response: yes we did try this but it did not work as intended.
For example, I choose Dr. X for my first submission, so he won't show up when I go in to complete the survey for a second time which works. However, when I choose Dr Y for my second submission & submit, it'll overwrite the embedded data to Dr Y, meaning that when I go in a third time, Dr X will show back up.
Essentially, it's not cumulative, it only notes the most recent choice you made.
You can use 2 embedded datas and use second one to update the variable in XM directory. Eg if embedded data people has one value then use another embedded data NewMember to add people as comma separated and then use this NewMember in workflow task.
In display logic you can use contains logic to make this work
Hi @Deepak, I’m working with Stephanie on this and wanted to ask a clarifying question - how would the value for “People” be set? We don’t necessarily have a value that we could assign before the respondent completes the survey for the first time. I’m also a little unclear as to how the ChoiceGroup/SelectedChoices aspect of the “New Member” field wouldn’t be overwritten with each time a respondent submits a response.
For context, respondents are required to provide feedback on 10 people but can go in 10 different times to submit feedback (selecting one person each time), if they wanted. We’re trying to figure out how to not have that embedded date overwrite itself each time.
I know it’s kind of a weird ask so let us know if it’s easier to connect using a different method to explain. We’re so grateful for all of your insights!!
You will be keeping people value empty for first and fill it via workflow in xm d so that next time when person comes it will autofill.
Secondly the new member embedded data wouldn't overwrite because if you see I have included people and the selected choice both comma separated so it will have new and old value both.
Then you will keep value of people as new member in xmd task in workflow.
I gotcha! That makes sense and it worked perfectly. Thank you again for all of your help, we really appreciate it!
@sarandos Kindly mark it solved if the answer helped you.
