topic Re: Why is Collector crashing on Windows and Android App when trying to work with related tables? in ArcGIS Collector Questions

Why is Collector crashing on Windows and Android App when trying to work with related tables?

TracyDeGrazia — Fri, 27 Oct 2017 14:08:07 GMT

Hello,

I am having trouble with our collector App. It was working, and now it isn't. Everything works fine, until we try to add something to a related table, and then on both android and windows devices it either freezes the app or shuts it down completely. It works perfectly fine on ios hardware.

I have found a few resources, but none of them are helping us. Things i have done:

- enabled pop-ups

-made the relationship based on GlobalID's

-Changed settings in the service editor.

I found this article, and did everything associated with it. https://blogs.esri.com/esri/arcgis/2015/02/18/related-tables-exploring-new-ways-to-use-collector-for-arcgis/

We also tried some of the suggestions from this post, but the workaround with security is just not feasible for us.

https://community.esri.com/thread/121100

Thank you.

Re: Why is Collector crashing on Windows and Android App when trying to work with related tables?

Anonymous User — Fri, 27 Oct 2017 17:53:30 GMT

Tracy,

Is the relationship class GlobalID-GUID? The primary key is the global ID field and the GUID is the destination field.The global ID gets copied to the GUID field for the related feature. Are you using hosted feature services or services from ArcGIS Server? If Server, which version?

Re: Why is Collector crashing on Windows and Android App when trying to work with related tables?

TracyDeGrazia — Fri, 27 Oct 2017 19:54:18 GMT

Dan,

I have it going from globalid field to a globalid field. I created the global ID field in the related table through the menu under manage - add global id's.

And we are using data from arcgis server version 10.4.

Re: Why is Collector crashing on Windows and Android App when trying to work with related tables?

Anonymous User — Mon, 30 Oct 2017 12:30:51 GMT

Did you add globalIDs for both? That is fine, but I suggest you create another guid field in the destination feature, then recreate the relationship to point from the globalID field to the new field you created in ArcMap. This allows any new related records to contain the globalID from the parent feature.