Error when publishing "Unsupported relationship type"

Question

Hi,

I'm trying to use Survey123 Connect to create a new survey from a feature service. The feature service is a geodatabase with 3 tables and established relationships between them — 1 parent table with 2 child tables. I created the geodatabase and set the relationships in QGIS before exporting to .gdb and uploading into ArcGIS Online.

When looking at the item in AGOL, all of the tables are correct in the Data tab and all relationships between the tables are intact. When I create the survey, the fields from each table populate the .xlsx file and seem to each appear in the appropriate format (fields for related tables appear in repeats). Even though it seems that even Survey123 Connect identified all of the relationships correctly, attempting to publish the survey gives me this error. The field in question is an ID field in a child table, which is the field that relates to the parent.

Does anyone know how to resolve this? Do I need to use global ID's instead of the relationships I setup?

Thank you!!

dougbrowning · Answer

Other post is correct must have the 123 built in globalid to parentglobalid relationship there.  But what you can do is have both - which is what I always do. Second relate I manage the keys myself in the form.  Globalid is really not a good way to do relates.

I suggest making a copy of the form, remove submission url, and publish that to see what 123 wants then mirror that.  I had a whole write up on how to do this but the new community my links are broke.

Basically what I do is publish a form, download the GDB that 123 makes, add my own second relate, publish, point form to this new service.   You can do something similar by adding in the relate 123 wants and publish, then repoint.  If you have existing service with data then yea its a world of pain but it can be done if you move the data.  Make copies and test.

Hope that helps.

TylerGraham2 · Answer

Survey123 supports 1:M relationships only and you need to use Global IDs and in the child tables GUIDs to hold the parent Global ID that points back to the record in the parent table.

So that String in the key most likely needs to be a GUID field type.