I have a couple of GeoFence Synchronization Rules that seem to work when importing new features that were added to the feature service since the last sync, but they do not appear to detect when the feature backing a GeoFence has been deleted from the feature service. I would expect it to do this and automatically delete the corresponding GeoFence. Does this functionality exist?
Hi Curt,
I had a customer recently run into the same issue, and then I found the following bug:
BUG-000089545 : GeoFences are not synchronized when a feature is deleted from a feature service.
It looks like this bug is still relevant at 10.8.1. I did some testing and found that the only way to remove Geofences through the GeoFence Synchronization Rules is to designate a date field for the Time Extent End parameter.
@JakeSkinner or @RJSunderman - I am running into this very issue in v10.9.1. Deleting a polygon feature in the Feature Service feeding the GeoFence Synchronization Rule is not deleting the GeoFence from the list. i am using the "Replace All GeoFences in Category" choice.
I see that the bug mentioned above was fixed in 10.4. Is this a bug again in 10.9.1 - or is this the intended behavior?
Thanks,
--Adam
@AdamRepsher_BentEar -- Testing 10.9.1 (Patch 4) my advice would be to configure your GeoFence Synchronization Rule with the Replace All GeoFences in Category checkbox unchecked.
Changes made to address BUG-000089545 were not included in any 10.9.1 patch nor any of the earlier release patches. Changes to the logic for geofence synchronization for this bug were first incorporated into the 11.1 release.
A couple of things to pay particular attention to when testing:
Once you upgrade to the 11.1 release, because logic associated with the Replace All GeoFences in Category checkbox changes, my advice is to delete and reconfigure your GeoFence Synchronization Rule to make sure the Replace All GeoFences in Category checkbox is checked.