All edits made during an ArcMap edit session are tracked in the Lucity Edit Cache (The GBAARCED table in the GBAComm database). When the edit session is saved, the Lucity GIS Extension processes the Edit Cache and updates Lucity databases with the edits.
At times, a user may need to clear the Edit Cache. Clearing the cache can be helpful when:
It's taking too long to save the edit session after the user has run the Update Spatial Relationship and Force Synchronization tools.
Solution: After the Edit Cache is clear, the user can select a smaller number of features and rerun the Force Synchronization tool on the revised set.
The ESRI Field Calculate function is performed on a field that either isn't in Lucity or that Lucity doesn't need to update. These actions require the Lucity extension to sync every edited feature. In such cases, it takes the system extra time to process edits through the GBAARCED table.
Solution: Clear the Edit Cache after calculating the field to speed up the synchronization process.
A bad record exists in the GBAARCED table.
Solution: Contact a Lucity Support representative to confirm that a bad record exists and verify that the GBAARCED table can be cleared.
Important: When the Lucity Edit Cache is cleared, the system clears all records added by the current user. This means any edits cleared from cache will not be made in Lucity. The user must either: 1) perform the edits again in a new edit session or 2) run the Force Synchronization tool on the previously edited features to correctly update Lucity.
How To Clear the Lucity Edit Cache
Start an edit session in ArcMap. The person clearing the Edit Cache must be logged into Lucity as the user whose edits need to be removedfrom the cache. If you are not logged in as that user, restart ArcMap and log into the Lucity tools as the correct user.
Selecton the Lucity GIS Edit toolbar. A dialog will appear listing the number of features to be deleted from the Lucity edit cache.