In our survey we have created 2 versions of the same question because the customer wanted different wording depending on the user region in the sample file. So we have Q17.1 and Q17.2 which ask the same thing but slightly differently.
To report Q17 as a whole we created an embedded data field that populated after Q17.1/Q17.2 were completed, but we are seeing that the translated text is appearing in data & analysis, so if I select option 5 "Very good" and set my embedded data field to Q17.1 selcted answers, if the respondent takes the survey in Spanish data & analysis shows "Muy bueno" rather than "Very good".
How can I get the selected answers pipe in to pipe-in the answer value in the survey setup language (English)?
How to show answer choices mapped to embedded data field in default English?
+3jamesbyrneipsos Translations would be difficult because each embedded data field would need to be translated. Here's another option, and one I should have thought of first. Structure the survey as you had originally planned, but instead of merging the two questions using embedded data fields, use the Coalesce feature on the data and analysis tab. It's a much cleaner solution than I originally proposed.
+41jamesbyrneipsos When you pull in question responses into a embedded data field it pulls in the data as it appears at the time. What I would suggest is setting two embedded data fields to populate just one question text itself. One embedded data field would be the text for 17.1 and the other the text for 17.2. You would then set the question text as the embedded data field. You can branch logic the embedded data field in the same way you were setting your question to appear.
+3jmborzick So we would have just one single Q17 in the survey, where the entire question wording is a piped-in embedded data field? So branch if region = A then q17Wording = "ABC", and another branch if region = B, then q17Wording = "DEF"?
Then Q17 is just written as ${e://Field/q17Wording}?
It feels like this could get quite hard to manage with translations?
+41jamesbyrneipsos Translations would be difficult because each embedded data field would need to be translated. Here's another option, and one I should have thought of first. Structure the survey as you had originally planned, but instead of merging the two questions using embedded data fields, use the Coalesce feature on the data and analysis tab. It's a much cleaner solution than I originally proposed.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.