AnsweredAssumed Answered

canUpdateFeature returning false when geometry updated

Question asked by mikedmanak on Jul 11, 2019
Latest reply on Jul 19, 2019 by mikedmanak

When users save a record in our apps I check if the feature can be updated, and if not I add the feature instead.  In a recent app (100.5) we've noticed that if the user updates the (point) geometry canUpdateFeature is returning as false and triggering the creation of a duplicate feature in the geodatabase.

 

Is this the expected behavior?  Should I be detecting an existing feature in another way?

Outcomes