Hosted Feature Service Bug in iOS Collector App?

[RyanNosek]

When publishing a hosted feature service with 2 layers and feature access enabled, only one layer is editable in iOS Collector App. Both layers are visible in the Collector app map (e.g. both displayed and in layer TOC), but only one feature shown in "Create a new feature"/ feature template pane.

• Tested on iPad (iOS 9.0.2) and iPhone 5s (9.0.2)
• iOS Collector App release 10.3.5 on both devices
• If it helps - it second layer in the service that is visible/editable, e.g. Layer visible/editable is /1;  layer visible but not editable is /0
• The hosted feature service does contain a relationship class (the two being published layers share a one-to-many simple relationship)
• This same hosted feature service behaves as expected (e.g. both layers show, hosted feature service honors the relationship class as expected) in Android Collector App, ArcGIS Online web map, and WAB
• Publishing from ArcGIS for Desktop/ArcMap 10.3 (product version 10.3.0.4322)

Curious if this is might be an iOS Collector App bug related to Hosted Feature Services (not sure about ArcGIS Server Services having the same issue) and/or if anyone else has experienced this issue?

[RussRoberts · Accepted solution]

There is an option called "Filter Related Types" under the app settings that filters the child features from the template picker. This is in place to restrict the chance of creating orphaned related features. You can disable this option and it will allow you to create features for both the parent and child feature from the template picker with no restriction.

[RyanNosek]

Thank you! Didnt realize this option was present in iOS app and On by default (guess it is off by default in Android).

Follow up question, maybe for another post, but will try here first - with this same service that contains a relationship class, I'd like to copy the new feature from an existing feature (snap).  I know this option is possible when there is no relationship class present (e.g. "Copy"--> " At the same location; Different feature, copy location"), but was curious why this option is is not possible when there is a relationship class?  This is not platform dependent, same behavior on Android/iOS.

Thanks again for your quick reply

[RussRoberts]

Copy and continuous collect on maps with relationships. If you are copying a parent feature that is not GlobalID based you could then be copying a PK and break relationships, likewise a child feature could be a parent for another relationship and that would break the relationship. There are a few other workflows where Copy and Continuous Collect could break relationships and right it is disabled in the app. This isn't saying that support for these workflows will not be coming but we do want to make sure when it is added it will not break any data relationships.