Select to view content in your preferred language

domains bug - exports code not desciption (and yes I checked the environment setting to use Desciption)

554
2
10-23-2024 02:02 PM
Kevin_MacLeod
Frequent Contributor

So, I think this bug has been around for many years. Curious it was never fixed.  I called support and reproduced it.  Domain codes are exported when exporting data to a table or a Shapefile.  Yes, even when the Environment setting to transfer Domain Descriptions is checked.  This is true:

In ArcMap 10.8.2 and in Pro 3.3.2.  From both SDE (SQL enterprise geodatabase) as well as from file GDB from both ArcMap and Pro. Anyone else having this issue?  And I also tried copy and pasting from the attribute table out of both, into Excel.  All of the above, fail.  Only code is exported.  Bug?  Esri team, this is important and affects nearly every customer.  Support had no workaround or solution.

(update: bug is still in 3.4.3 in May 2025...)

2 Replies
VinceE
by
Frequent Contributor

Can't replicate. Can you be more specific about the tool you are using or what the issue is? I'm on Pro 3.3.1. Can't comment on ArcMap.

Here are two domains, one numeric, one text.

VinceE_0-1729782448283.pngVinceE_1-1729782456302.png

Here they are applied to a FeatureClass:

VinceE_2-1729782493694.png

Exporting to Excel:

VinceE_3-1729782525087.png

Export shows the descriptions, not the codes. This doesn't work for you?

VinceE_4-1729782560230.png

 

0 Kudos
Kevin_MacLeod
Frequent Contributor

Still have this bug. It's a severe bug. At Pro 3.4.3. What I meant was, export to SHP does not work. Shapefile.  Domains do not transfer descriptions to Shapefile or to Table. 

 

 The only workaround was Table to Excel GP tool. Curiously, this tool and this one only, transfers domains, and obeys the Environment setting. I wrote a model to join back by GUID and recalculate in the model all the descriptions.  A rather tedious workaround to create but once it's done it works fine. I repro'd this while on phone w Support. Perhaps it's some combination of our data, database, and Arc version.  Hopefully they can figure it out.  Is anyone else in the same boat?  

 

It's curious why Preserve GUIDs and Transfer field domain descriptions are not enabled by default. Kind of like how unique layer IDs are not On by default. I would think more folks would want all these On by default; than the opposite.

0 Kudos