Survey123 Not Linking Related Table through Repeats Properly on ArcGIS Portal

[JeremyEisch]

I am looking for help resolving an issue where Survey123 is not linking a related table through a repeat properly. I have a feature service published to ArcGIS Portal with a feature class and a related table. They are linked with a relationship class that has a primary key of GLOBALID and foreign key of PARENTGLOBALID. I have created a feature services survey using Survey123 Connect to edit this service. The issue I am encountering is when I submit a new survey using the web form in a web browser it works perfectly fine but if I try to do so using the Survey123 mobile app, the GLOBALID in the feature class doesn't match the PARENTGLOBALID value in the related table. From what I've read, it appears that I need to have the 'Use global ID parent keys in repeat relationships' option enabled when I publish the survey however that option doesn't show up when I publish using Suvey123 Connect version 3.19.104. Any help resolving this issue would be greatly appreciated.

[DougBrowning]

Sounds like you made the service then connected the form to it?

You list uppercase field names but the fields 123 adds are actually lowercase  globalid and parentglobalid.  I have seen this be an issue but I have also seen that of you try and change this in the backend Arc thinks they are the same.

As a test I would create a brand new form and use the file option to copy your current form.  Take out any submission url if there is one.  Publish this as a new form.  Look at the schema it makes and compare.  Then add a submisson_url in this new form pointing to your current feature service and see if it gives an error.  That will give you some more clues.

Hope that helps

[JeremyEisch]

Hi Doug,

Thanks for the suggestion. You are correct, I created the service and then connected the survey form to it.

Unfortunately trying this didn't work. I was hopeful as I was able to publish the form with the 'Use global ID parent keys in repeat relationships' option enabled however when I added the submission url back in it didn't seem to retain the option. We did try re-creating the feature class and related table with lowercase globalid and parentglobalid fields however our SDE seems to automatically change them to uppercase. I find this scenario very bizarre as it works perfectly fine in the web form.