Hello!
My colleague Ian McNair and I have been around the ringer trying to figure out an issue with a survey we created on a related table. As far as we can tell, the survey was created successfully - meaning new submissions appear in the related table and as long as the GlobalID from the point feature is pulled in using URL parameters, the related records are associated with the point feature.
That being said, any time a submission is made to the survey, a new "ghost" point feature is also created. This feature has no geometry and the only attribution is what pulls in through the URL parameters. What's also odd is this feature also has no relation to any records in the related table.
The workflow we used for creating the survey is as follows:
Creating the Survey
- Using Survey123 Connect, created survey from an existing feature service hosted in our organization's Portal (not ArcGIS Online).
- Removed all fields related to the point feature and the repeats, leaving behind only the fields of the related table.
- Under the Settings tab of the excel sheet, updated the form_id to match the name of the related table as it appears in the service URL.
Tying into a Web App
- In a web application (Web AppBuilder), I created a custom popup on the point feature to include the Survey123 web form link.
- The survey link also pulls in the following URL parameters from the point feature:
- Company - as a read-only field for the user's reference - into the related table's "company" field
- GlobalID - to maintain the relationship between the point feature and the record in the related table - into the related table's "ibp_u_id" field
-----------------------------------------------------------------------------------------
Once we have the survey set up for submission, we can't understand why we're getting the behaviors below:
- Scenario 1: Everything configured exactly as described above
- The survey successfully pulls in the point feature's Company and GlobalID fields.
- Upon submitting the survey:
- The submission appears in the related table
- When clicking on the point feature, we can see the submission as a related record
- The submission generates a new feature in the point feature service. This "point" does not have geometry and contains the Company and GlobalID field pulled in from the URL parameters - all other fields are blank.
- Scenario 2: Remove the Company field from the URL parameters
- The survey successfully pulls in the point feature's GlobalID field
- Upon submitting the survey:
- The submission appears in the related table
- When clicking on the point feature, we can see the submission as a related record
- The submission generates a new feature in the point feature service. This "point" does not have geometry and contains GlobalID field pulled in from the URL parameters - all other fields are blank.
- Scenario 3: Remove the Company and GlobalID fields from the URL parameters
- Upon submitting the survey:
- The submission appears in the related table but is not related to any point feature
- The submission generates a new feature in the point feature service. This "point" does not have geometry and all other fields are blank.
-----------------------------------------------------------------------------------------
We're not sure where to go from here or how to identify where the hangup is. We've also tried republishing new services in the case something became corrupted behind the scenes but in the end we're still getting the "ghost point" that shouldn't be there.
Any help is greatly appreciated - we're ready to get this working so we can roll it out! James Tedrick? Ismael Chivite?
Resources:
Survey123 Web Form (XLSX file attached)
Web Map
Web Application
Published Feature Service - Portal Item
Thank you!
- Lea Harper
