nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multiple Relationship Classes in ArcCollector?

deleted-user-9a0OAqlztHcy

I am setting up inspection reports connecting to their fields in arcCollector, I have hydrants working with its inspection field and followed the same steps to set up hydrant valves and valves, however the second two are not popping up with relationship class data (inspection reports) in arccollector when i go into the fields. Can anyone offer me a clue on why the second two are not working? Can only one relationship class exist in ArcGis online maps?

Find more posts tagged with

Accepted answers

deleted-user-9a0OAqlztHcy

Figured it out: So to do this, you must make seperate GDBs with each having their own feature and relationship class in them, add them to a final map and that is how it will actually run

All comments

Anonymous User

Codi, you can have multiple relationship classes in Collector.

https://blogs.esri.com/esri/arcgis/2015/02/18/related-tables-exploring-new-ways-to-use-collector-for-arcgis/

Did you include all the related tables in the map document before publishing? Also, how did you construct the relationship classes? One-to-Many, One-to-One? What about the fields you used as the Primary and foreign keys?

deleted-user-9a0OAqlztHcy

That is actually the article i based it on, I made the relationship classes step by step following that guide, the defaults were how i based everything. The three tables all published, the hydrant feature is the only one showing up with the inspections sector under it though

Anonymous User

Cody,

Do you have two separate features in your map? I am curious how you have things set up. Hydrants->Inspections and valves->valve inspections are separate? Could you outline your relationship class setups?

deleted-user-9a0OAqlztHcy

Yes I do have three separate features in my map: Hydrants; Valves: Hydrant Valves. Hydrants have a relationship class too Inspections: Hydrants; Valves have a relationship class too Inspections: Valves; Hydrant Valves have a relationship class to Inspections: Hydrant_Valves. Thank you for answering so quickly

deleted-user-9a0OAqlztHcy

Figured it out: So to do this, you must make seperate GDBs with each having their own feature and relationship class in them, add them to a final map and that is how it will actually run

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.