Linking to Hosted Feature Layer Clarification

GarrettRSmith

Hello

I am working with a point, line, and polygon file given to me by a client that they would like to use as the geographies for three different Survey123 forms that will be used to collect data related to each. 

I am following the advice of @DougBrowning outlined in this post:

https://community.esri.com/t5/arcgis-survey123-questions/mapping-with-survey123-within-a-polygon-or-admin/td-p/836112

I have followed all the steps but am still confused. My confusion is outlined below.

When I publish one of the forms from Survey123 connect the Feature Service has a point feature layer (there is no geography question on the form so this I assume is the default) and the two related tables created from repeats in Survey123 Connect XLSForm. The default point file does inherit three of the questions from the XLSForm because I do not have those questions set up to be repeats, so they attach to the default point feature layer.  When I made my .gdb in Catalog, the polygon feature that I am trying to use as my geography does not have these fields so when I try and link to the hosted feature layer and update the survey it will not allow it because it cannot find the originally created point files table. 

Is it advisable to create repeats for all questions and to have the polygon only have a field that will relate to the three tables (two already created plus the new one)? In the two existing repeats I have a parentglobalid field that is populated from Field Maps from the polygon's GlobalID field. Also, can I not include the default point file in the new hosted feature layer?

Thanks for any clarification on this matter.

dougbrowning

You need to match the FormID in settings to the table or FC in the service.   123 always make a feature service since well its Esri so everything is spatial.  You can convert it to a table before you publish if you want and it will work.

For the relate you do not have to use parentglobaid if you are not using repeats.

Basically each form is dumping into a table in the new service you published.  The forms do not care if other layers are in the service.  The form only adds data to the tables and leaves the polygons alone.  You get the relates to work by passing the keys into the form using URL parameters.  At least in my examples the polygons are all know and not edited so keep them out of the form.  123 can dump the data into any layer or table in the service as long as that FormID matches it will find it.  Make sure you are using the submission URL.

I hope that helps.  I cannot really tell where you are going wrong here yet.