Issue with existing app after upgrade of Survey123 from 3.15.151 to 3.15.156
My client is using Field Maps and Survey 123 against Hosted Feature Classes in ArcGIS Enterprise (10.9.1 - fully patched). Their solution has worked well for the last year, but the recent rollout of Survey123 v3.15.156 (on iPhone) has caused issues.
Scenario:
My client uses ArcGIS Field Maps to view master asset data. Arcade scripting is used within the popups. A user selects an asset from the map, and the popup presents a hyperlink to "collect a survey". The hyperlink passes key attributes from that asset to a survey form in the iPhone Survey123 App. The Arcade generates the following:
itemID={ITEMID}
&field:parent_globalid={DA978BCF-2026-4882-B466-3E6D2A2B4BD3}
&field:mastid=XYZ
&field:catchment_id=1234
&field:sitepoint_id=1234
&field:asset_id=XYZ_SW000004
&field:center_latitude=-41.34862717
&field:center_longitude=174.75089489
&field:inspection_number=2
&field:statusfield=statussurvey02
Survey123 at v3.15.151 would open, and the downloaded survey form would also open. The form would be pre-populated with the above (passed) attribution. The user would then enter condition information and other attributes.
Everything was great until the update to 3.15.156. Following the upgrade, the Field Maps component was ‘fine’ and would make the call to Survey123 in the same way, but depending upon the user the result would be either:
The second view says "survey not found", but it was confirmed that the surveyid number presented related to the survey_sanitary survey that was in the list above the error.
My client has the configurations for the above available in ArcGIS Enterprise (pre-prod and prod) and also ArcGIS Online. Testing showed that the above error only occurred in the ArcGIS Enterprise environments. Therefore, as their third-party support, I was called in to diagnose the ArcGIS Enterprise issues.
Some testing showed that at the point of ‘failure’ there was no call from Field Maps or Survey123 to the ArcGIS Enterprise environments. There was nothing in the IIS logs to show that a request was made at that time. i.e. the testing in pre-production was out of hours and the environment was quiet.
The survey had originally been configured so that a user could not ‘start’ the survey from Survey123. The workflow ‘had’ to come from Field Maps. For clarity, if the user opens Survey123 they would see the downloaded survey. When they selected it, they would be presented with metadata of the survey, but the following button was not available and they could not open a form to complete the survey:
Once we had proven that ArcGIS Enterprise was not being called at that time, the client set about making changes in the way that Field Maps integrates with Survey123.
The release history:
has been reviewed, but nothing stands out.
Changes to make the application work:
1) The Arcade in the popup was updated to pass an additional parameter:
&action=collect
2) In Survey123 Connect the options were changed to enable the “+ Collect >” button shown above.
3) Certain fields in the associated survey were set as read-only. The GlobalID of the master asset would typically be passed and populated in the form. Because this field is read-only it cannot be populated by the user. Arcade has been used to present a message stating that "the survey could not be submitted" (because the value was null). A validation was put in place to prevent this forms contents from being posted to ArcGIS Enterprise.
Request
The solution works, but the UX is not quite the same as before. It would be interesting to know what has changed in the new release that is causing these changes to the User Experience. It would also be good to know what can be done to return to the original configuration.
Accepted Solutions
