Collector app has stopped populating the foreign key field when adding a related record offline.

Question

I have had running a data collection system using the collector app for about 6 months. Recently the foreign key in the related table has stopped populating when working offline. It works fine online.

E.g Sign post (ID 123), Add issue, Issue feature class (Foreign Key = NULL).

I think it might be since the last android update.

Has anyone else had this problem? Any ideas?

Thank you

VickyS · Answer

After a lot of testing I have worked out that it is to do with the fact we have multiple relationships to the same feature class (issues).

E.g. Site to Signs, Signs to Issues populates the foreign key correctly

Site to Signs, Signs to Issues AND

Site to Bridges, Bridges to Issues does not populate the foreign key field in offline mode in for issues recorded against either the Bridges or Signs feature class.

This has been working for the last few months and the check system is about to go live so something has changed. Can anyone replicate this?

Thank you

VickyS · Answer

No filter related is on. I've recreated the map from scratch too and still get the problem.

ahkim · Answer

Maybe Filter Related Types setting is turned off and you are creating orphaned records?