topic Re: Foreign key in related table not automatically populating in Collector (?) in ArcGIS Collector Questions

Foreign key in related table not automatically populating in Collector (?)

HaileyMonod — Fri, 15 Apr 2016 17:49:00 GMT

I have recently run into the issue of the foreign key not automatically populating in the related table, when creating a new record with collector. It appears to work when editing in ArcMap on my desktop, however it’s not working on the collector app. I am using a Global ID in the original feature class and a corresponding GUID field in the related table to ensure the 1:M relationship.

I am using ArcGIS Collector v 10.3.9 on iOS and publishing services with ArcGIS server (v 10.03) on amazon EC2, then configuring web maps with ArcGIS online.

Please let me know if you can help or have any advice on how to resolve this issue.

Thank you!

Re: Foreign key in related table not automatically populating in Collector (?)

VickyS — Mon, 18 Apr 2016 08:23:15 GMT

Yes, I have this exact same problem. I have logged it as a support call with ESRI UK. This set up used to work but has recently stopped.

My work around was to redesign the database and set up 1:1 relationships. From what I worked out it is something to do with the having more than one 1:M relationship to the same table (same destination table).

Collector app has stopped populating the foreign key field when adding a related record offline. - No one has answered it though!

Re: Foreign key in related table not automatically populating in Collector (?)

HaileyMonod — Mon, 18 Apr 2016 21:49:46 GMT

Thanks for sharing Vicky. I have also started a support case with ESRI Canada.

Unfortunately, I need the 1:M relationship for this project. So hopefully something can be worked out. Please let me know if you find a solution.

Re: Foreign key in related table not automatically populating in Collector (?)

VickyS — Tue, 19 Apr 2016 07:28:09 GMT

I have got this sort of set up working

Bench to BenchIssues (1:M)

Sign to SignIssues (1:M)

But it does not work if you just have 1 issues table. e.g

Sign to Issues 1:M

Bench to Issues 1:M

It used to work but we have had to redesign the database at the last minute and create separate issues tables for each feature class. I will let you know if I hear back from ESRI UK.

Re: Foreign key in related table not automatically populating in Collector (?)

HaileyMonod — Wed, 20 Apr 2016 22:24:29 GMT

HHhhmm its odd, as I only have Hydrants to HydrantInspectionsTable (1:M) and its not populating the FK in the table, when creating a new record using collector.

Re: Foreign key in related table not automatically populating in Collector (?)

CallumSmith — Fri, 22 Jul 2016 01:25:23 GMT

I have just come across this issue as well. Collector with Portal and ArcGIS Server 10.3.1.

My schema is (all GlobalIDs/Guids)

MudPits(fc) 1:M CleaningEvents(table) 1:M Attachments(table)

Works fine in desktop but not in collector. Has anyone figured out a solution for this??

Re: Foreign key in related table not automatically populating in Collector (?)

JohnDeLoretta3 — Wed, 27 Jul 2016 15:30:04 GMT

We ran into this issue today, and discovered that the Foreign Key and GlobalID fields were turned off in our related tables in the MXD we use for publishing our services. Turning those fields back on and republishing the services fixed it for us.

Re: Foreign key in related table not automatically populating in Collector (?)

TórshavnarKommuna — Thu, 14 Nov 2024 17:07:55 GMT

I encountered the same issue and found a solution, which worked for me.
Having the same feature class published as multiple layers with different symbology in my web service caused the problem. When I created a new web service with the origin and destination tables each represented as a single layer, the issue was resolved.