Select to view content in your preferred language

Experience Builder + Survey Widget Issue

198
3
Jump to solution
Wednesday
IrelandHackman
Occasional Contributor

I've created a Feedback form for an Experience Builder that I've been working on. I created the survey in the Survey123 Connect app and was able to publish it successfully with no issues. However, once I used the Survey widget to import the survey, all the questions that had conditional viewing settings were visible.

The first question I had was based on which age group a survey participant was part of, so most of the questions will be hidden if the user is less than 13 years old (due to FTC guidelines). Therefore, we don't want any questions to be visible if the user is less than 13 years old, so I had the following code in the column labelled "body::esri:visible" to prevent certain questions from being visible. ${Age}!='<13'


This worked well and as intended within Connect, but when I imported the survey into the Experience Builder, those constraints no longer seem to exist. I also wanted these constraints to be present so text boxes for questions where people could elaborate on why they chose "other" would be hidden unless "other" was selected.

If anyone could help with any settings that need to change to make this function as intended, it would be much appreciated. I've included the .xslx form so that people can try and replicate this issue. 

 

Thanks in advance!

0 Kudos
1 Solution

Accepted Solutions
Neal_t_k
MVP Regular Contributor

Try changing this:

selected(${Purpose}, 'purp_other') AND ${Age}!= '<13'

to this:

selected(${Purpose}, 'purp_other') and ${Age}!= '<13'

 webform is more sensitive to syntax being correct

View solution in original post

3 Replies
Neal_t_k
MVP Regular Contributor

Try changing this:

selected(${Purpose}, 'purp_other') AND ${Age}!= '<13'

to this:

selected(${Purpose}, 'purp_other') and ${Age}!= '<13'

 webform is more sensitive to syntax being correct

IrelandHackman
Occasional Contributor

Thank you so much; that solved the issue! I wasn't sure one thing would make the whole situation function as intended, but that is the very nature of code. I appreciate your help. 

Neal_t_k
MVP Regular Contributor

That was a weird one, but then I noticed it worked on the first couple questions but not the rest.