Exporting Feature Class with GlobalID from Enterprise SDE to a table, globalID's are removed

[BenVan_Kesteren1]

I have a Rubbish_Bins feature class in my SDE, this has GlobalID (type is Global ID) column as per below screenshot:

You can see all the global ID's are populated.

I then run the Copy Rows tool in Arc Pro (right click | data | export table):

I open this CSV and I note the global ids are all removed, yet all other columns are populated.

I then tried testing this in ArcMap 10.6.1

I open the attribute table, click export, then use these settings:

Then i get this error:

Note this error is only happening on this feature class (its the only one I have added GlobalID to).

Am I doing something wrong here or is this a bug?

Thanks

[MatthewCriel]

ESRI... Its time to fix this!

[Robert_LeClair]

Matthew - I pulled up BUG-000117958 and it's listed as "under review."  As I do not work for Support Services or the ArcGIS Pro team (I work in Training Services), I do not know when it will be fixed.  The proposed workaround is to use the Table to Excel GP tool.  That's all I've been able to find.  Not great news I know, but news nevertheless.

[RobertTaylor5]

I have this problem when using Export function from within attribute table in ArcGIS Pro 2.9.5.  Global ID field is definitely set in the table, but the exported *.csv file has null data. 

And why is it when someone notes that this is already been logged as a BUG does the problem get marked as SOLVED in this forum?   

This problem is years old and still  not solved!  

[JessicaJThompson]

Hello @RobertTaylor5,
Yes. It is very frustrating....

My work-around that I have used a few times is I create a new field GlobalID_copy. Calculate the field to = the GlobalID field. Then when you export to xls/csv they do not get deleted and you can copy and paste them back into the GlobalID column.

Excessive but it does get the job done.
Hope it helps!

[RobertTaylor5]

Thanks Jessica.  I tried a different workaround: I exported the table as a dbf instead of csv and then just changed the dbf extension to csv.   For some reason, the Global ID is correctly exported in that case. 

But enough with workarounds!

Esri. Are you listening?  How about fixing this???

[Becca_]

This is still a problem in 2023?? 5 years later..

[Robert_LeClair]

@KoryKramer - do you know if there's an update to this BUG-000117958 - it's listed Under Review.  Thx!!!