AnsweredAssumed Answered

Collector: 1:M related table without having to re-type PK value in FK field

Question asked by fimpe001 on May 8, 2015
Latest reply on May 8, 2015 by canadiantodd

When I insert a record into a related table via Collector my foreign key value is not auto-populated, as this blog and the comments suggests. Any suggestions for where to start troubleshooting this, or how to configure this correctly?


The relationship class is based on a GlobalID field and a field of type GUID. The above referenced blog states "foreign key should be set to a new, unique GUID field." What is meant by a unique GUID field? In a 1:M relationship the foreign key field cannot be constrained to unique values, or else it would be a 1:1 relationship.


My setup: ArcGIS Server 10.3, Geodatabase 10.3 Oracle 11g, web map with 1 versioned point feature class, a related table, and attachments. Pretty much as simple as it can get. Thank you!