I've been running a survey (published from Survey123 Connect) for over a month that had "required=yes" and the conditional visibility set in the "body::esri:visible" column; it performed last Tuesday without issue. This Tuesday--after doing the most recent Connect app update on Friday, and without making any changes to the survey / XLSform--the survey is failing to submit and seems to be enforcing "required=yes" questions that are not visible. As a temporary fix, I have moved the conditions to "relevant", but I need the data to NOT all be deleted if the questions are revisited, since the survey is being completed by students (who are accustomed to being able adjust a response as needed without losing another). None of the questions are in a repeat.
I saw this post: Survey123 Web: body::esri:visible vs required but it does not address this issue as of the current update.
nevermind, somehow this all boiled down to case of the choices. Previous surveys would not work unless the visible query was evaluating on the label which had capital letters in it, now it is is evaluating on the actual choice code which is all lower case
There is already a fix out in early adopter. https://earlyadopter.esri.com/project/article/item.html?cap=e69ef91f45744b98882c651f7b518eb7&artid=d...
the 123 team is so fast!