Hello James,
I am creating a workflow that would do something very similar, with one important distinction.
We will be utilizing collector to gather inventory of a utility pole, and it's related table components that exist in one feature service with the Poles Feature Class and it's related component tables (Cross Arms, Insulators, etc). Then, we will be inspecting those assets in survey123 that is built from a different, existing feature service that contains an All Inspections Feature Class and the related Pole Component Inspection Tables (Pole Inspection, Cross Arms, Insulators, etc).
I've got the relationship classes down, indexing figured out and an appropriate guid field to pass the Global IDs of the Pole & it's attached components to, but have one major question I am concerned about now.
Say we have 2 cross arms on the pole, and I need to pass the two cross arm Global IDs that will show from the popup of the pole (pulled from the cross arm component related table) into two separate repeats within the PoleCrossArmInspections table(repeat) inside of survey. So Cross Arm A sends the Global ID into the CompRel_GlobalID Guid field of the first repeat in that table, and Cross Arm B sends that Global ID into the CompRel_GlobalID Guid field of the second repeat in that table.
Is this possible at all? If not, do you have any ideas for a work around?
The structure of the relationships are established as this, with GlobalID being the parent keys and Rel_GlobalID being the foreign or child GUID keys. Then, there is a third relationship class that links the GlobalIDs of the Cross Arm Inventory Table (blue) to the CompRel_GlobalID GUID child or foreign key field of the Cross Arm Inspection Tables.
COLLECTOR (Feature Service 1) SURVEY123 (Feature Service 2)
Poles FC (Inventory of Poles) (GlobalID) All Inspections FC (GlobalID)
(Rel_GlobalID)-Related Table Cross Arms (GlobalID) -------->(CompRel_GlobalID)Related Table Cross Arm Inspections
(Rel_GlobalID)
Thanks for your consideration here.
Evan