When populating a Survey the fields with Default values AND 'exclusive' Relevant expressions do NOT populate or transfer when surveys are submitted. The issue relates to BUG-000115589 raised in 2017 and modified in 2021 but not resolved.
So essentially what happens is any data that is NOT relevant is excluded even though default. In my case I have multiple Boolean questions using 'esriFieldTypeSmallInteger'. If the question is NOT relevant I still need it to parse a '0' on survey submit in the JSON that is uploaded to the server. Otherwise you are left wondering if the answer was 0 or 1 or did something go wrong in the survey or data transfer process. In my case I now have to look through hundreds of surveys and photos individually and make/verify decisions for at least 10 fields and hundreds of row records.
I am looking for a some type of logic implementation that may help me circumvent the issue in the future and override the surveys' decision to exclude the data on transfer. While the answers may prepopulate the entire survey on initiation, the use of relevant fields then 'cleans' out the default values leaving a blank.
Running my own bug resolution tests in Survey 123 Connect clearly shows the JSON to be uploaded is missing answers to those 'irrelevant' questions entirely. While that may seem logical to not include data, it is also logical to have a default 0 value so I know a decision has been made and the answer populated. That way I am not left guessing if there was some other issue occurring in the survey.
The sort of solution I need here is one that does not come with logic complications that must then be resolved with more logic to solve a simple request.
Things I have tried;
1. set bind::esri:parameters to 'auto' but that did not work
2. applying calculation logic to check if the field had ben cleared back to '' based on the radio button event removing the default value of '0'. Problem was I didn't get the right logic happening. And it is usually important to have an event to make a calculation occur. I have not totally given up on this approach though.
3. removing 'relevant' expressions from the Group Begin (which was important as it was designed and required to ensure surveyors are not looking at and or getting confused with irrelevant selection options).
This ONLY worked for fields that had NO subsequent relevant expressions. It did not work for any other fields which had default values of 0.
4. removing Relevant expressions altogether... my current thoughts here
Maybe an alternate approach is to NOT use the issue causing 'relevant' column.
I will have an attempt at triggering an event that simple 'hides' the field on the form but does not 'remove' it from the data. Any ideas on this approach would be welcomed.
Thankyou for your time.
