Hello, this is a continuation of a previous query I had posted earlier.
I am trying to update 3 fields based on the input in the repeat section. While resolution_status_latest and resolution_last_update is correctly displaying values from the repeat records, the resolution_last_officer is not updating.
When I open the repeat record in the Survey123 app, it does not show the value that was selected in code_officer when the repeat record was created.
Any help would be appreciated.
Thanks!
Solved! Go to Solution.
Just got this resolved with help from Esri tech support. What finally worked (though we are not sure why given that resolution_status_latest and resolution_last_update updated without any problems) is the following:
for resolution_steps, changed bind::esri:parameters from query to query allowupdates=true
Hope this helps others in the future. Thanks for all your help @DougBrowning and @ChristopherCounsell!
I think it is not updating as you add records since it does not see it.
I would try adding calculationMode=always in the bind::esri:parameters field on resolution_last_officer. If that does not go add to the resolution_count also.
See here for more info https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-calculation-modes/...
Hopefully that does it
Thanks @DougBrowning!
Unfortunately, those changes did not work. I am confused why the Code Officer radio buttons show up unchecked in the submitted record. Somehow the selection I am making in this while submitting the repeat record (it is a required field) disappears from the saved record. I am starting to wonder if this is why the resolution_last_officer field also fails to auto-populate.
I just looked at the record in the Survey123 web interface and the input for code_officer in resolution_last_officer and are recorded in the table. For some reason they do not show in the app.
Very confusing!
Are you setting it to the name value vs the label value?
@DougBrowning I tried both. As I discovered, the values are recorded in the database but, for some reason, not showing up in the app interface.
Wait I see now its just a regular field not working not anything to do with index. Can I see that list? Maybe some sneaky special chars in there.
It is also working correctly on the Survey123 Connect app. The correct values are only missing on the mobile app.
mmm do you have this query allowUpdates=true on the begin repeat line in bind::esri:parameters column?
@DougBrowning I have query in the begin repeat line in bind::esri:parameters, which I need to be able to see the collected records in the Inbox.