Latest Contributions by ShelbyZelonisRoberson

Hi - I've built a survey in Connect (3.12) and I'm having trouble with one part of it. My end goal is to have the survey PREVENT submission if a geocoded address field (${matchaddress} is null. Seems easy right? I thought I could create a select_one yes/no ${validaddress} field, calculate it to be 'no' if ${matchaddress} is null and 'yes' if ${matchaddress} is not null, and put a constraint on this field so that it will not let the user submit a record if ${validaddress} = 'no', but it doesn't work. It lets me submit a record even if the matched address is null and validaddress is no. I've also tried various iterations of this using ${matchaddress} = null, since it should have the same result. No dice. What's weird is that if I put ${matchaddress} = 'null' in the relevant column, the ${validaddress} field either shows or doesn't show exactly as it should. So why isn't the constraint working the same way? I've worked on this for days and days and I feel crazy and I'm really hoping someone on the Survey123 team can briefly work with me and take a look. I'd prefer to email my XLS rather than share here. Thank you! ... View more

I've created a public survey in Survey123 (Enterprise/Portal version) in which a user can input an address via geopoint and then submit the survey. There is a hidden field in the survey called District. Upon survey submittal, I have an attribute rule set up via ArcGISPro that immediately calculates the District that the address falls within and edits the District field in the feature class with this correct district value. (The survey data is based on a feature class in a SQL EGDB that is registered with my Portal so that's how I'm able to do this). In Integromat, I want to be able to watch for the survey submittal and then create a report. This seemed easy....but my problem is I need the calculated District field value to show up in the report. The only options I seem to have to populate the report are from the "Watch Survey" module, which has a null District field because it's null immediately upon submittal, even though the feature class gets populated via attribute rule very shortly after. I tried a bunch of workarounds (sleep tool for 30 secs after watch survey, watch for Edit instead of Add) but the problem I'm running into is that I need to be able to choose the District field from the survey feature class after it is edited, and not the immediate survey input values that are available in the "watch survey" module. Help?! I feel like I'm so close but so far. *NOTE* I originally was doing this with custom javascript in my survey, which worked great because the District field populated BEFORE survey submittal. Unfortunately this survey has to be public so I can't use that method. 😞    ... View more