the first line will not respect the REQUIRED condition while the third will. The first line is a select_one, the third line is a Text. Both have the Required column at YES and both have conditions in the Relevant column. Any clues why the select_one causes the Required to fail?
What version of Survey123 Connect and App are you using? We currently have a few known issues with required fields in version 3.3 release which we are aiming to resolve for 3.4. It is likely the issue you are seeing coudl be related to these known bugs.
Can you please provide a copy of your xlsx file so we can take a closer look?
Open this post in a new window, not in the Inbox, and then hit reply and use the advanced editor link which is in top right hand corner of reply, there is option in editor to attach files:
Thanks Rene, I got your xlsx file and did some tests.
See my response below to Mohamad, there are two known issues affecting your survey to do with required fields and expressions/validation not currently working correctly.
Rene logged a case with Esri Canada. I'm working with him to investigate this issue.
I was able to replicate on my end as well. It seems to occur when the question is a select_one question and it has an expression in the 'Relevant' column. Regardless whether the required column is set to 'yes' or an expression, you will always be able to send the survey without selecting an answer for the required question. I was able to replicate the behavior in another survey as well.
This is a known issue with required expressions on select one questions, currently only input questions (text, decimal, integer) are supported with required expressions due to a regression bug, which we are aiming to resolve this in the 3.4 release update.
There is also another known issue in play with Rene's survey, it has already been logged as BUG-000120023 - The required select_one questions with a 'relevant' field do not validate in Survey123 for ArcGIS. This is related to any required question which uses relevant not validating correctly, regardless of whether it uses a simple yes configuration or expression. We are also aiming to resolve this in the 3.4 release.
At this stage we are targeting the next release for mid-May, but this could change depending on how many issues are still outstanding and required to be included in this next release.