Image-Map selection as choice filter

[michael_vetter]

I'm trying to create a survey where the users select different choices from an image map and I use the selections as a filter in the choice filter column. The image map is a select multiple question so I know I have to use selected() in the choice filter. During my testing, I noticed that when I select the first choice the filter works properly, but any other choice doesn't display until I unselect an additional choice. I'm not sure if this is a bug or if this functionality works with an image map. I've attached my form from the image map sample.

[abureaux]

Any chance you can include the image map as well so I can test this locally?

[michael_vetter]

Thanks for the response. I've attached the SVG that's being used.

[abureaux]

Unfortunately, choice_filter limitation for image-map questions. Seems like an odd limitation given that an image-map is just a different way to display select_one/multiple.

That said, there is a (silly) workaround. Just add a hidden select_multiple (a regular one) and in the calculate column, reference the image-map question. Then, you can make your choice_filter point to that new question. Problem solved. Here is an example:

As for this part not working:

That is just a limitation of select_multiple. The workaround is to add every option to its own calculate. Then concate them all together. Then finally trim the trailing ", ". I actually just did that today. Here is an example:

[michael_vetter]

Thanks for the reply and finding a potential workaround. However, the workaround isn't working for me. I've copied what you've done in the screenshots, but I'm still getting the same behavior as before. I'm using Survey123 Connect version 3.21.62 so could it possibly be a version issue?

[abureaux]

That is the most recent Connect version (which I am also on).

Well, I was going to just upload my XLSX, but upon checking the workflow again, it's now no longer working for me either... maybe I just got lucky yesterday.

This behaviour seems unintentional, so I'd suggest calling Esri Support to log bug. Once you have the Bug or Enhancement number, you can post here in case others have the same issue.

Sorry. This is super frustrating since it's already so close to being supported!