I'm trying to integrate an application with Survey123 using the documentation found here:
In our application, users will be presented a map of features from a system of record (SOR). From there, they may decide they want to update that record with new information gathered from the field. For the field work, we're using ArcGIS Survey123, which has the benefit of isolating the field data in a Feature Service, allowing the field data to be reviewed before loading it into the SOR.
The features from the system of record are polygons, many of which have been created by buffering points. Thus, they have too many vertices to be passed to the ArcGIS Survey123 field app in the URL using the `field:fieldName=This%20value` syntax.
This workflow seems to work well with the Survey123 Web App. Using the `?mode=edit&globalId=uuid` style query, the app opens up to the new feature. However, when I try to carry this same logic over to the Field App (which is what our requirements call for), the app keeps opening to an empty form.
I've created a super-simple survey and shared it publicly to exemplify the issue in this CodePen:
FWIW, the S123 form we're trying to get to production has many repeats. However, we're not trying to carry over any of the repeat fields from the SOR.
Does anyone know what's going wrong here? Why can't I open a feature that would be in the inbox without using the inbox?
The documentation seems to imply that this is a viable solution.
Thanks for reading!