I have a feature service that contains structures (points) and conveyances (lines). The conveyance feature has both an upstream GlobalID (GUID) and a downstream GlobalID (GUID) field to store the appropriate ID from the structure feature. The relationship classes created to facilitate field data collection via Collector are:
Collector enforces the parent/child relationship by requiring the user to first create a structure, then add the conveyance. However, both options available in the "Related" section (screenshot below) of the attribute pane lead the user to create a "Downstream Conveyance" feature (populating the downstream GlobalID field in the conveyance). Originally, I thought I may have selected the wrong relate because Collector does not display the name of the relationship class. But after further testing, both options populate the downstream relationship. At first glance, it seems that Collector is ignoring the other relationship entirely even though it is present in the feature service. I attached a copy of the JSON from my Structures and Conveyance layers in the feature service.
Has anyone else experienced a similar issue in Collector and found a solution? Is this a bug? Or am I missing something?
Thanks in advance,
I just built another one point to 2 tables relationship and a third going from one of the tables to a third table.
Try simply doing it in Catalog or ProCatalog and not use code
Thanks, Robert. My relationships are from one point feature to two attributes in a line feature. I will try to do this via Pro and see if I have different results when publishing. The JSON was attached for reference.