I’m not sure if this is a bug in FME or if it’s expected behavior. We work in versioned, replica file geodatabases. The issue that has presented is that when our data was being checked back into the Enterprise database, the change records in our replica were being applied to features outside of the AOI of replica. In other words, somewhere in our FME processes it was not managing the OBJECTIDs in the INSERT/UPDATES/DELETES tables correctly.
We believe we have tracked it down to the ‘Fast Deletes’ parameter of the FileGDB Writer. From my research it looks as though this truncates the tables, and re-inserts the features that weren’t deleted. I’m also reading that this may cause issues because it bypasses the A/D change tables. This tracks with the errors we are seeing.
Is there any validity to that? If so, I’d like to suggest that the Fast Deletes parameter be defaulted to ‘No’ instead of ‘Yes’.