I am running the latest version of Connect (3.1.126) and the Survey123 Field app (3.1.158), but I am still running into BUG-000117394. I am not sure why I am still receiving this error. I am passing the GlobalID from a feature service that has three different parents layers that are in a Collector map via a URL scheme to a GUID field in a related table that is related to all three of the layers. I am able to pass the GlobalID successfully to the Survey but when I submit my survey I receive the follow error, "The INSERT statement conflicted with the FOREIGN KEY constraint." I am not sure if I am missing something. thanks for the help.
I've followed up to a comment version of this question in https://community.esri.com/groups/survey123/blog/2018/11/02/st-kilda-penguin-release-31?commentID=68... . This looks to be an issue with the index on the GlobalID field of the table.
I didn't want to start a new thread, since my issue is directly related to BUG-000117394, and I wasn't sure where I might receive an answer first. I already commented on the thread, for which you provided the link above, but I am going to outline my problem here as well. Any help is greatly appreciated 🙂
I still struggle with BUG-000117394 "The INSERT statement has conflicted with the FOREIGN KEY constraint" error (see attached screenshot).
I followed the following work flow:
I initially created the survey using Survey123 3.9, but I re-published using the latest version. Any ideas what I am doing wrong? One thing I am not entirely sure about is: I might have added the attribute index to the GlobalDs AFTER creating the relationship classes. would that matter at all?
Thanks a lot for the help.
I just started getting this same error myself...