Support many-to-many relationships in ArcGIS Collector

[JakubŠilhavý]

We would appreciate than Collector can work with data models which use many-to-many relations and special case of one-to-many relation, where the origin is in the table and destination in feature class.
 
Using standard geodatabase model for editing related data in ArcGIS Collector brings data model consistency cross all applications in ArcGIS platform. That means, that it would be easier to work with, and would not be necessary to change data model to collect data in Collector for ArcGIS.
 
 

[ScottPrindle]

When promoting this idea, please consider supplying a use case where many-to-many or one-to-many relationships would be used in conjunction with Collector for ArcGIS.

Thanks,
Scott

[JakubŠilhavý]

We have two use cases:
1) Our user is an officer checking the trees on city parcels. He has an evidence of trees, bushes and grass plots. He is mainly in offline mode.
In terrain, he needs visit the trees and checks their state and save these information to his database.
For these purposes, he uses Feature Classes with related tables. e.g. Trees FC, Checks Table, TreesTypes Table.
Trees-to-Checks is one-to-many relation (origin in Trees – working good in Collector), TreesTypes-to-Trees is one-to-many relation (origin in TreeTypes – is not displaying in Collector).
 
2) Our user is an auditor of bike trails. He has an evidence of trails, road signs, bike racks, owners of trails and other trail’s infrastructure. He is mainly in offline mode.
In terrain, he checks the state of trail’s features and save these information to the database. He collects new features on trails.
There is many-to-many relations in data model.
Trail-Sign: The road sign can be placed on cross of two or more trails and on one trail can have more road signs.
Trail-Owner: The owner can own more trails and the trail can be owned by more owners. Owners are stored in table, trails are stored in feature class.