How to preserve the original ObjectID among feature types with ArcGIS Data Interoperability?

645
2
Jump to solution
06-08-2023 08:59 PM
ThaoNDP
New Contributor III

Hi everyone,

I am facing a problem.

While transforming data from a feature class to another feature class between different FGDBs, how can I retain the original ObjectID in the destination feature type? Because this ObjectID field I am using in a Relationship Class, therefore, if after transforming data, the new ObjectID is generated, I am afraid my Relationship Class will no longer work properly.

I am aware that it is necessary to use the GUID field for the Relationship Class instead, but assuming we are only working with the GlobalID field.

Thank you very much for any advice on my case.

Regards,

ThaoNDP

0 Kudos
1 Solution

Accepted Solutions
RenatoSalvaleon3
Esri Contributor

A colleague also suggested another geoprocessing tool to migrate the relationship class to your destination gdb.

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/migrate-relationship-class-t...

Then do ETL that retains GlobalID.

View solution in original post

2 Replies
RenatoSalvaleon3
Esri Contributor

There are Pro tools (Import/Export XML workspace, Copy/paste from the Catalog pane) that can help preserve the OBJECTID from a source fgdb to a destination fgdb. Could you just use those Pro tools first to move the original data set into the new fgdb and then use transformation on the new fgdb?

If your workflow requires you to do this with ETL, I am not too clear how you are going to use that relationship class from one fgdb to another. Maybe I misunderstood. Do you intend to create that relationship class on the destination fgdb as well? Working with geodatabase with Data Interop does not support the creation of relationship classes, they have to be created from Pro first. Here's an article with video on this topic: 

https://community.safe.com/s/article/writing-geodatabase-relationship-classes

For an update workflow preserving OBJECTID, please read this community article from the Safe Software community asking a similar question.

https://community.safe.com/s/question/0D54Q00008X71AKSAZ/how-to-retain-objectid-in-gdb

 

 

 

 

 

RenatoSalvaleon3
Esri Contributor

A colleague also suggested another geoprocessing tool to migrate the relationship class to your destination gdb.

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/migrate-relationship-class-t...

Then do ETL that retains GlobalID.