Using Survey123 Connect. Survey published/to be published in ArcGIS Online. Not using an existing feature service but layer will be created as part of the survey. Users will 100% be using the browser for the survey--no requirement to download the app.
Our Sustainability Department is doing a Clean Air Giveaway event in which box fans and high quality filters will be given to residents of our City. Apparently the last event had a more than noticeable number of non-residents so they are hoping to use a geofence during registration to help prevent some of that (the reality is that one will never eliminate non-residents participating without a lot of vetting).
I have successfully set up the pulldata (@layer) to query the address to determine if in our city limits, using our custom site address locator. The locator contains only addresses within city limits plus a handful for areas in which we provide service such as water. It works well but as with all locators, sometimes an address isn't indexed or the user doesn't put in enough of the address to meet the minimum match thresholds, so we'd like to add a question asking, upon determining the address is not within the City, if the user believes it is an error. If 'yes', I'll mark a hidden field [not yet added to the survey] to indicate this was a rejected address but allow the user to fill in the form just so we have the info when Sustainability reviews the address.
This survey has added a number of new elements for me to learn how to implement, but I believe my logic is sound with how I've structured the questions/grouping for this. But in testing I am unable to submit the survey because the initial determination is that the address is outside the City. To be clear, if the user is honest and says they are outside the City, we want there to be a full stop and survey not move forward. That currently works as intended.
As a side inquiry, I concede that perhaps I am not testing properly for a constraint or relevant field entry. My constraint for determining if within the City is string-length(${CheckWithinCity})>0 and that functions properly. I haven't been able to determine what the return value is if the address is not even found in our data. I attempted to use "is null" but when I saved the Excel file Connect did not like that syntax. It accepts a string-length...=0 but I don't know if that is a proper value.
So, is there a way to override the 'out of city' determination and still allow submitting if I structure the follow-up question(s) appropriately? I appreciate any insight!
[Attaching my .xls. City limit service and locator are public. Test addresses: IN City - 130 E Sunset Way; OUT (not even in dataset) - 10334 240th Pl SE ]