I am working with some Esri Workspace XML documents supplied by a third party. These have (for years) successfully loaded via python into Personal GDB for minor attribution before being imported into the enterprise GDB.
Now our database structure is changing and I have been tasked with creating an FME translation to read these XML files and write them into the new structure.
I have discovered, however, that FME drops or ignores the first record for every feature class in the XML. It appears that the Workspace XML files have an ObjectID
0 for the first feature in a feature class (much the same as in a Personal), but FME seems to want them to start at ObjectID
1 (like a File GDB or Enterprise GDB).
How can I get FME to accept the ObjectID
0 features? There is nothing wrong with these features - they will import into Personal GDB no problem, and if I change the
0 to another number like
999 in the XML they are read by FME no problem, but since they are value Esri XML files I would expect FME to be able to see them as is.
Currently I have a workaround that re-numbers the
999 before we run the FME translation, however this isn't a great long-term solution.