Query Layer Reassigns Unique ID on Data Export

[JustinShepard]

I have a query layer that is coming from SQL Server. The table has a unique ID field that is not sequential; which I am able to use in ArcGIS when setting up the query layer. The issue is that when the data is exported to a feature class ArcGIS makes the field into the ObjectID field (rather than creating a new ObjectID field) and writes over the IDs that my data was using. This makes it almost impossible (without adding another field to my table in the database just to store the original ID) to relate the data back to the original table.

Is there a way to force ArcMap to add a new ObjectID field rather than overwrite my data? Why isn't this the default behavior?

[MandarPurohit]

I encourage you to contact technical support regarding the question �??Is there a way to force ArcMap to add a new ObjectID field rather than overwrite my data? Why isn't this the default behavior?�?�

In the meantime, one workaround (to add a new ObjectID) could be to export the query layer to a shapefile and then import the shapefile to ArcSDE.

- Mandar

[BrentPierce]

We are currently working on a solution to this problem. One possible workaround is to choose another field (or collection of fields) to be used as the Unique Identifier of the query layer when the query layer is created.

Hope this helps,
-Brent