While I was exploring option with Contact List Trigger, I was glad that ContactList can be used like a table (in database) where we could use to update our own data in Qualtrics.
I guess only limitation for the ContactList is that it has to have an email address associated with it that if we try to update something, it should designate who did the update.
Is there way we could bypass who did the update, and use another ContactList as purely a table we could use for multiple users can use to update data on each survey question and retrieve updated data on the outcome from that question (no matter who answered the question)?
Page 1 / 1
A contact trigger will only update the contact that took the survey (via invitation or authentication).
It can create a new contact for a non-authenticated contact.
TomG Thanks for your feedback.
When you refer to "via invitation", are you referring to regular Emails options such as "Individual" or "Multiple Completes"?
Regards to "It can create a new contact for a non-authenticated contact.."
When we export the output of the survey, do we have a separate report from the original Contact List and the newly generated file (a new contact) and.. how is the outcome look like (what type of information does a new contact have)?
JustinD - Are you creating a survey, where a contact embedded data in a contact list gets updated every time anyone completes that survey?
rondev - Basically, I am trying to have a surveyor (subordinate) completes the survey and then a manager goes in to the survey and sees the answer that subordinate answered and updates the answer if necessary (manager has to see the result on the survey).
I realized that the 'multiple completes' accomplishes somehow by having one to update data later again, but it does not give other person (manager) to update on the same question (other than seeing the different response history from exporting the survey result).
Is there any solution?
Leave a Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.