Setting up for repeat inspections on existing point.

[MalloryCarpenter1]

I am looking for some help in setting up what I thought was a fairly straightforward task.   I am using portal. I have an existing hosted feature class that represents infrastructure locations on which we need to complete regular inspections.  I would like to have the inspections in a related table, and I do not need to collect a new point with every inspection, so ideally the survey is only passing answers to the related table.  

I set up my survey following the instructions here: https://community.esri.com/t5/arcgis-survey123-blog/working-with-existing-feature-services-in-arcgis...

The inspection questions are in a repeat, I set the form=id setting to my related table, and removed all questions prior to the repeat.  I have set up field maps to use a custom attribute to link from the feature to the survey, and to pass along relevant information such as the feature ID.  This process resulted in a sort of free-floating table that is no longer related to my feature class.

I switched tactics to try using the inbox.  Only 36 of my 75 points show up, the test survey answers show up in the related table, but they aren't linked to the related point.  Also the point disappears from the inbox map once I've completed one survey.

Ideally I would prefer the field maps workflow as there are other feature layers I would like displayed on the original map to which I would link the survey.

Is there some documentation for this sort of situation that I am missing?  I've cobbled it all together out of various blog entries and other help posts but I don't feel like getting closer to a solution.

Thank you!

[MobiusSnake]

This process resulted in a sort of free-floating table that is no longer related to my feature class.

Something went wrong at this point.  It sounds like Survey123 Connect published a new hosted feature layer rather than linking to your existing layer and its related table.  You mentioned setting the form_id value, but did you also set the submission_url value?

[MalloryCarpenter1]

Yes, I set the submission_url to that of the original feature class.

[MobiusSnake]

It's hard to say what went wrong at that point if both the submission_url and form_id were set, but I'd focus on trying to sort that out.  I've used that pattern on many projects and it's worked well.

You mentioned removing all the questions prior to the repeat, did you remove the repeat itself as well?

Also, what did your submission URL look like?  You'll want to ensure it looks like this, and not the URL to the feature service that's on the page in the web interface (that ends in /FeatureServer):

https://yourorg.maps.arcgis.com/sharing/rest/content/items/your_item_id_here

[JenniferAcunto · Accepted solution]

How is your relation set up? Is it using globalIDs? If so, your Field Maps link needs to send the globalID of the parent feature into the parentglobalID field of the related table. 

[MalloryCarpenter1]

This was the answer!  Thank you!