Hello ​@Mark d.,

If you look at the screenshot, you’ve added the Embedded Data as ‘Selected hospital’, but while setting the condition below, you’ve used ‘SelectedHospital’. Please note that embedded data fields are case-sensitive. Try correcting this and test it again.

Let me know if this helps.

Thanks ​@Sachin Nandikol. SelectedHospital is now consistently applied in the logic, however the preview show’s I still haven’t cracked the problem. I have checked the question ID wasn’t faulty by recreating the question and replacing the new question number. Is the text of the Embedded field coding correct?

Could you please share a few more screenshots of the survey flow and the survey . This will help us understand the issue better and assist you more effectively.

Thanks ​@Sachin Nandikol 

Here are the screenshots.  

Mark

Hi there, wondering if any Qualtrics pro-users are able to help me solve this logic programming puzzle involving drill down questions.  See screenshots above. ​@Sachin Nandikol ?

Hello ​@Mark d.,

Remove the piped value of youe ED and add below, it should solve your issue:

${q://QID187/ChoiceGroup/SelectedAnswers/2}

Let me know if this helps.

HI ​@Sachin Nandikol 

I’ve replaced the ED with the suggested text, however in preview mode, the survey continues straight on to section B as shown above.

I’ve double-checked that there are no extra spaces after SelectedHospital in either entry.

Very curious about the source of the glitch!

I hope you have published the new changes and then testing it. I have replicated the same and it’s working for me with the suggested text. Now even I am curious to know what kind of glitch it is. Can you just create a dummy test survey and try if that works or just remove your survey branching and redo once. I think it could be bug or glitch.

Dear ​@Sachin Nandikol 

Sorry for the hassle! I hope this is at least providing you with some sense of intrigue!

The problem persists despite removing/replacing branch logic and republishing. I tested in both preview mode and using a survey link in a new browser window.

I also created a dummy survey of the key elements (QID187 replaced with “QID1”), but the preview and survey link tests also failed (progressed straight on to rest of survey).

I notice that I am never able to see the QID for the drill down question in the list of options for piped text. “Q187” is the original number that Qualtrics allocated for this item

For some reason I can no longer upload images of the survey flow from the revised survey and the dummy survey.  Is there another way to send you these on the forum, or by another means?

Regards

Mark

That's quite interesting—it's not that it's not working, but when I try it on my end, everything seems to work perfectly. I created a dummy survey, and it functions as expected. For your reference, I’ve included a screenshot of my survey flow below.

You mentioned you also created a dummy survey—could you please share the QSF file with me? I'd like to import it into my sandbox environment to investigate further and see what might be causing the issue.

If you're unable to share it here, feel free to send it to my email. I've also sent you a message directly.
 

Hello Mark,

Thanks for sharing the details and QSF. I have imported it to my account and when I tested it didn’t work for me as well. After inspecting I noticed that in survey flow ED value is been set as ‘MY HOSPITAL IS NOT LISTED’ but if you see in the dropdown it’s actually ‘MY WORKPLACE IS NOT LISTED’. Once I changed this value to workplace the flow is working as expected. Below are screenshots for your reference:
 

Hi ​@Sachin Nandikol 

Thank you for picking this up! 

Swapping “workplace” into the condition now makes the dummy test work properly.

Bizarrely, the main survey still doesn’t branch to Block H, despite removing and replacing the branch and then publishing. Yikes!

Here is a side-by side of the glitchy survey and the now-functioning dummy test.

Will need QSF of that survey to investigate further. 

​@Sachin Nandikol, truly appreciate your assistance here! ​@Mark d., were you able to resolve your issue?

We’re working on it ​@AlonsoC .  Will post an update on the solution after discussing further with ​@Sachin Nandikol 

Hello ​@Mark d.,

Its just a bug, remove that question and add a new question. it will work. 

Thank you ​@Sachin Nandikol for your help cracking the case of the faulty drilldown question.

I also learned some new tricks, including how to list the QIDs under the tool menu and examine the data and analysis tab to prove data wasn’t being captured for the faulty item.