All edits made during an ArcMap edit session are tracked in the GBAARCED table in the GBAComm database. When the edit session is saved the Lucity GIS Extension process through the GBAARCED table updating the desktop application with the edits.
Sometimes it is necessary to clear the edit cache. Some typical reasons may include:
Saving edit session after running the Update Spatial Relationship and Force Synchronization tools is taking too long to process.
After the edit cache is clear users can then re-select a smaller number of features and then run the Force Synchronization tool on the new set.
An ESRI Field Calculate is performed on a field that either isn't in the desktop or the desktop doesn't need to be updated with the values. This triggers the Lucity extension to sync every edited feature. Thus, saving edits will take additional time processing through the GBAARCED table.
Clear the edit cache after performing the field calculate to speed up the sync time.
A bad record exists in the GBAARCED table. It is recommended to contact a Lucity support representative to confirm that a bad record exists and the GBAARCED table can be cleared.
Important: When the Lucity Edit Cache is cleared it will clear all records added by the current user. The desktop application will not be updated with edits that are cleared from the Lucity Edit Cache! The user will either need to perform the edits again in a new edit session, or run the Force Synchronization tool on the previously edited features in order for the desktop application to get updated correctly.
How To
Clear the Lucity Edit Cache:
Start an edit session in ArcMap. It is important to be logged into the desktop application as the user whose edits need to be remove from the Lucity Edit Cache. If not, restart ArcMap and log into the lucity tools as the correct user.
Selecton the Lucity GIS Edit Toolbar.
A dialog will appear listing how many features will be deleted from the Lucity edit cache. To continue and have the records removed, click Yes.