topic Re: Cannot publish survey when visibility rule based on single choice question response is applied to note in ArcGIS Survey123 Questions

Cannot publish survey when visibility rule based on single choice question response is applied to note

MadiWoodrum — Fri, 02 Feb 2024 07:55:19 GMT

I have a Note element in my Survey123 form that I only want to be visible when participants respond with any choice in a Single Choice question other than one certain choice. I saved and published the survey before applying the visibility rule, and no errors occurred. After I applied a visibility rule to the Note (*question* IS NOT *choice*), the survey could be saved but not published. An error message occurred requiring something to be done to the visibility rule on the Note. After some trial and error, I found that no matter what the visibility rule on the Note was, it would prevent the survey from being published, and I could only publish the survey without a visibility rule on the Note.

Re: Cannot publish survey when visibility rule based on single choice question response is applied to note

abureaux — Fri, 02 Feb 2024 18:52:41 GMT

try not(selected(${question},'my one choice'))

EDIT: And if that doesn't work, can you please provide your XLSX so we can see how the note's visibility is set up?

Re: Cannot publish survey when visibility rule based on single choice question response is applied to note

MadiWoodrum — Fri, 02 Feb 2024 19:35:48 GMT

We are in the ArcGIS Online Survey123 platform, not Connect. A non-GIS, community engagement employee is managing the survey and isn't familiar with Survey123 Connect.

Re: Cannot publish survey when visibility rule based on single choice question response is applied to note

abureaux — Fri, 02 Feb 2024 20:02:03 GMT

Darn. Sorry, I don't have much experience with the web designer. To limited for what I tend to need.

Re: Cannot publish survey when visibility rule based on single choice question response is applied to note

MadiWoodrum — Mon, 05 Feb 2024 15:58:33 GMT

Thanks anyway! I'm pretty sure it's a bug.