CamM I think you have misunderstood the problem. Qualtrics is creating the bad data. It has nothing to do with my Salesforce field definitions. I use other tools to integrate with Salesforce (e.g., Formstack forms) and map the exact same values to the exact same fields without issue. Qualtrics is parsing a choice that contains commas and replacing the commas with semi-colons.
CamM Indeed the picklist values and the API Name are identical in this case. The problem is on the the Qualtrics side, though, as their "black box" is deciding how to identify, escape and\\or replace delimiters.
Edit to add : Are you able to use the Contact External ID in an upsert (vs insert) of the related object record?Disclaimer : I have not tested this end to end with a Qualtrics survey and workflow. But I did put together a Record Triggered Flow that may address this scenario and very limited testing was successful. This flow utilizes an External ID (unique) field on the Contact and a matching External ID (unique) field on the related object to link the two objects. The flow is fired when a new related object is created and 1 - Contact ID (that is the lookup field) is null2 - External ID field on related object is also nullThe flow has two steps:1 - Get the Contact record with matching External ID2 - Update the related object with the ID of the Contact retrieved in the first step
"I would like very much want to avoid to have a formula field on my CASE or CONTACT object"This may be the correct solution in this case, though. Objects don't have org awareness as far as I know. Adding a formula field solves this problem.
I struggled with this through my first couple of Salesforce integrations in Qualtrics and now follow these steps:In the Distribute Survey task, Add or remove embedded data fieldsHere you create the Embedded Data Field - I usually just drop the "__c" from the Salesforce API name (tough to see in this screenshot) :Then it's over to the Survey flow where if I recall correctly you must use the same case as in the previous step:Is this the right or best way to do it? I don't know but it works. The Qualtrics documentation deserves a review and rewrite by a real technical writer.
Thanks for the suggestion KimothiSaurabh . The styling is certainly helpful for display purposes but it has no effect on the submitted response. The XML payload looks like this"value": "\\"Hispanic, Latino, or Spanish Origin\\"",which does not work. That is, the Multi-select picklist is populate but with values determined by splitting the field at comma delimiters. The Qualtrics implementation is simply not very robust when it comes to determining if commas are present and taking action to properly escape or wrap these values in quotes.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
