Multiple Feature Classes to One Related Table

06-24-2020 10:34 AM
New Contributor II

I have a point, line, and area feature class that I want to relate to one monitoring table.

I have created GlobalID in the feature class and GuID in the table. 

Simple relationship classes between each feature and the table using 1:M, GlobalID to GuID, and forward messaging.

Feature Class Area > Simple Relationship Class 1:M, GlobalID to GuID, and forward messaging > Monitor Table 

Feature Class Line > Simple Relationship Class 1:M, GlobalID to GuID, and forward messaging > Monitor Table

Feature Class Point > Simple Relationship Class 1:M, GlobalID to GuID, and forward messaging > Monitor Table

This works as designed in the ArcGis Pro desktop but when published and used in Collector I get the error "1 or more attributes failed to submit" when trying to add a related event. 

Is this functionality possible? Am I doing something wrong in the configuration? I don't particularly want to create a static merge after the fact...



0 Kudos
5 Replies
Regular Contributor

Hmm - I know we've done something similar in the past... essentially creating a single inspection feature class related to multiple parent feature classes.  Is it possible you are having issues with the data types in your ID fields not matching up?

0 Kudos
New Contributor II

If I have one feature relate only to one table it works perfectly (i.e. Area>Relationship>Table), but adding multiple relationship classes seems to break it in Collector. How did you set up your related IDs, did you use global to GuID or something different? 

0 Kudos
MVP Honored Contributor

I have 9 to 13 related Feature classes to one main feature class and it works fine.  I use my own IDs though and not globalid.

I do not use globalids for keys for all the reasons in this post 

Hope that helps

0 Kudos
New Contributor III

I am having the same issue described using Field Maps and the Edit widget in the Web App Builder; when trying to add a record to the related table under this exact setup, the application(s) are unable to submit.

Is there an explanation for why a GloablID related to a GuID may not function properly within this setup?

I posted my own question asking this:


0 Kudos
New Contributor III

I tumbled around with this issue for a while. The problem seems to be same name on the ID-attribute fields.
I have to feature classes with defined relationships to one inspection table. The relations are based on GlobalID. My solution was to define different attribute fields in the relate-table. The relationships are:
GlobalID -> GUID_Polygons
GlobalID -> GUID_Points

In my original setup, I had the same attribute field - GUID. The relations worked fine in ArcGISpro. In Field maps, I saw established relations, but could not add new.
With this new setup, I can add and delete features and rows in Field maps. And I can take data offline.