Export related table doesn't show domain descriptions

[JillHalchin]

I published a layer for Field Maps on our internal GIS portal (10.8.1) that consists of a point feature class and a related table.  Some of fields in both use domains.  I collected test data then downloaded the results as both a file geodatabase and as an Excel workbook.  I need it in table format like Excel in order create paper output of the attributes. 

Looking at the tables in the exported geodatabase in Pro, I see the descriptions in the domain-controlled fields.  In the Excel export, those fields also show the description in the features attribute table, but the related table has the codes.  Why are they different? One works and the other doesn't?

Bug?  Suggestions?

[KathleenMarkham · Accepted solution]

This article might be helpful for you: https://support.esri.com/en/technical-article/000012394

It sounds like your two different export types (a File Geodatabase and an Excel workbook) may be experiencing what is described in that article regarding a similar export situation:
"The CSV file does not retain the description of domains because domains are a property of a file geodatabase. When exporting to any data type outside of a file geodatabase, the domain descriptions do not get exported ... instead, the coded value is exported to the output CSV file."

[DougBrowning]

Table to Excel tool has an option to get the domains.

https://pro.arcgis.com/en/pro-app/latest/tool-reference/conversion/table-to-excel.htm 

You may be able to use the 123 reporting feature even as a regular service.  We do some paper looking stuff with Data Driven Pages as well.  If the data is in SDE then I just add it to Excel directly as a live time link to the SQL db.  Have also made some with ReportLab.

Hope that helps

[JillHalchin]

Table to Excel works, so I'll build it into the workflow.  I need to keep this as simple as possible for the people who will be collecting data with Field Maps.  They'll be using the Excel tables to generate paper reports.   But I still find it strange that the exported feature class table and standalone table are different.