topic Re: Survey123 Web: body::esri:visible vs required in ArcGIS Survey123 Questions

Survey123 Web: body::esri:visible vs required

SMDSAdministrador — Tue, 06 Sep 2022 20:53:54 GMT

Hello everybody.

First, sorry for the bad English (Google Translate).

I have a problem with required questions controlled by the body::esri:visible column on the web. What happens is that, when the condition is not satisfied, the obligation remains. This prevents the form from being submitted (because the required question was not answered) at the same time the question is not displayed (because the condition was not satisfied).

The test form illustrates this situation: if I say that I don't want to display the 'next question' (required and controlled by visible column), Survey123 gives an error when submitting. However, if I withdraw the requirement, the form is successfully submitted.

(view in My Videos)

In all the posts and walkthroughs I've read, my understanding is that visible controls a question's visibility and calculations (and I agree with that). However, it doesn't make any sense for the question to remain mandatory even without being displayed, because this practically makes the use of this function unfeasible.

I would like to know if this is expected behavior from Survey123 Web or if there is anything that can be done to work around this situation.

Thank you all

Re: Survey123 Web: body::esri:visible vs required

Katie_Clark — Tue, 06 Sep 2022 21:04:03 GMT

First off, Google translate did an awesome job! English was flawless 😉

I know in using Survey123 Connect you can conditionally set a question as required if certain criteria is met. See this post for some more info. Hope that helps!

Re: Survey123 Web: body::esri:visible vs required

IsmaelChivite — Tue, 06 Sep 2022 22:00:41 GMT

Alternatively, you can also move your body::esri:visible expression to the relevant column and leave your question as required. If a question is not relevant, it will not be shown, its contents will be cleared, and the required and constraint expressions will be ignored.

Re: Survey123 Web: body::esri:visible vs required

DougBrowning — Tue, 06 Sep 2022 22:17:00 GMT

This was fixed when published from connect in the past. Maybe it has not been fixed in the web yet?

Re: Survey123 Web: body::esri:visible vs required

IsmaelChivite — Wed, 07 Sep 2022 15:48:58 GMT

@DougBrowning You are correct. This 'should' work in the web app. I logged an issue so this can be addressed in the future. In the meantime, the relevant workaround may do for @SMDSAdministrador

Re: Survey123 Web: body::esri:visible vs required

SMDSAdministrador — Thu, 08 Sep 2022 13:23:40 GMT

Google always saving us! 😂

I often use conditional binding on forms filled out in the field app, but I didn't know it worked on forms filled out on the web as well.

Thank you so much for this! I believe it will solve this problem.

Re: Survey123 Web: body::esri:visible vs required

SMDSAdministrador — Thu, 08 Sep 2022 13:43:40 GMT

Yes, Ismael. I agree that, in general, the relevant solves most problems (as in the simplified test form I attached above). After all, if I don't need to calculate a value for the question, why use the visible column?! I completely agree.

However, some of our forms are a little more complex and a hidden question can be calculated automatically or not, in the same form (depending on previous conditions). Thus, only the relevant does not meet the needs. But good to know that for the future this will be fixed on the web as well.

For now, @Katie_Clark solution to using conditionality in the required column resolves the issue well.

Thank you all!

Re: Survey123 Web: body::esri:visible vs required

Ruth_JiatengXu — Thu, 15 Dec 2022 06:29:31 GMT

Hi @SMDSAdministrador

Thanks for raising the issue, and the issue you mentioned has been fixed on current prod environment. The required constraint will be ignored if the question is hidden using body::esri:visible.

Please test with the url parameter ?version=latest if version lock is used.

Thanks,

Ruth

Re: Survey123 Web: body::esri:visible vs required

SMDSAdministrador — Mon, 26 Dec 2022 12:30:52 GMT

Ruth, we've run some tests and the problem seems to have been resolved. The requirement is being ignored.

Thank you for that.

Re: Survey123 Web: body::esri:visible vs required

DougBrowning — Tue, 14 Mar 2023 20:56:19 GMT

@SMDSAdministrador This seems to have come back in the 3.17 update that just came out. Can you test it again?

Here is mine breaking

Re: Survey123 Web: body::esri:visible vs required

SMDSAdministrador — Thu, 16 Mar 2023 13:30:16 GMT

Hi @DougBrowning

Yes, you're right. I performed a test publishing in Connect version 3.17.54, filling it with the Field App and I was able to reproduce this problem. However, in the Web App this does not happen (behavior is as expected, with required being ignored)

I think this is the first time I've seen correct behavior on the Web and erratic on the App 😅

Re: Survey123 Web: body::esri:visible vs required

DougBrowning — Thu, 16 Mar 2023 14:47:19 GMT

The 123 team is on it. Still trying to figure out the exact as it does it only on certain forms. For now I added some logic to my required to handle this.

If you figure out what is tripping it up let me know. thanks

Re: Survey123 Web: body::esri:visible vs required

DougBrowning — Fri, 17 Mar 2023 14:07:18 GMT

There is already a fix out in early adopter. https://earlyadopter.esri.com/project/article/item.html?cap=e69ef91f45744b98882c651f7b518eb7&artid=d1b41e7ad0f14054aab29ab1c1c06b69

Re: Survey123 Web: body::esri:visible vs required

DougBrowning — Wed, 22 Mar 2023 14:07:15 GMT

Update to 123 dropped today and it seems to be fixed. That is exactly one week turnaround! The 123 teams rocks!

Re: Survey123 Web: body::esri:visible vs required

AbdulabnanMohammed — Mon, 18 Sep 2023 10:29:53 GMT

@SMDSAdministrador & @DougBrowning

Is there any sample Form to try ...

I'm going to have a similar kind of Approach..

Thank You