Select to view content in your preferred language

Can't export global IDs as string after update to 3.2

1181
5
Jump to solution
11-27-2023 06:15 AM
Labels (3)
Emils
by
Emerging Contributor

When exporting from geodatabase, I usually change GlobalID field type to text so it would preserve global IDs. After update to ArcGIS Pro 3.2. changing field type does not work - it automatically sets back to GlobalID type

1 Solution

Accepted Solutions
Emils
by
Emerging Contributor

Option "Preserve Global IDs" was disabled. I enabled it, did the export to .gdb and after that did another export, changing field type to text, and it worked.


Yes, using field calculator to calculate global ID values into text field is an option, but in my case it would not be advisable. To get the job done I exported data as shape file and appended it back to blank geodatabase with domains.


I guess there is some issue when exporting from enterprise geodatabase to geodatabase, but doing two exports are good enough solution for now. 

 

View solution in original post

5 Replies
Hillary_E
Esri Contributor

Hi @Emils ,

 

What format are you exporting to? Are you getting any messages?

0 Kudos
Emils
by
Emerging Contributor

I'm exporting to geodatabase. No messages. Field type automatically sets back half a second after I have changed field type and pressed OK (icon switches from ABC to ID).

Capture.PNG

Hillary_E
Esri Contributor

@Emils ,

Is "Preserve Global IDs" disabled in the Environment settings of the export tool? Is it disabled in your project's Environments settings? This can be checked under the Analysis tab in the main ribbon > Environments (in the Geoprocessing Options) > Scroll down to "Geodatabase Advanced" and you will see the option to disable "Preserve Global IDs".
If it is disabled and this continues, a workaround you could try (before exporting) is creating a new field (as a text field) and using the field calculator to populate this field with the GlobalID values.

0 Kudos
Emils
by
Emerging Contributor

Option "Preserve Global IDs" was disabled. I enabled it, did the export to .gdb and after that did another export, changing field type to text, and it worked.


Yes, using field calculator to calculate global ID values into text field is an option, but in my case it would not be advisable. To get the job done I exported data as shape file and appended it back to blank geodatabase with domains.


I guess there is some issue when exporting from enterprise geodatabase to geodatabase, but doing two exports are good enough solution for now. 

 

VojtechC
Occasional Contributor

Hi, thanks so much for the advice on the Environment settings. That helped me a lot.

For me it works for exporting a Feature Class and for exporting a geodatabase table. But it doesn't work for exporting the table to CSV!

My workflow:
RClick on the layer in Contents Pane --> Data --> Export Table --> FilePath\...\TableName.csv

All rows in the CSV file have GlobalID set to zero.

A related topic identifies this as a bug that doesn't seem to have been fixed for several years...

------------------------------------------------------------------------------------------------------------------------------

WORKAROUNDS:

Looks like I found two possible workarounds so far.

  1. Using the Table to Excel GP Tool. GlobalIDS are preserved in the Excel table.
  2. Exporting the table to a geodatabase table (RClick --> Data --> Export Table, Environments setting "Preserve Global IDs" MUST be checked) and then exporting the table to CSV (Environments setting "Preserve Global IDs" DOES NOT NEED to be checked - weird)
0 Kudos