BUG-000133759 for ArcGIS Pro

Bug ID Number	BUG-000133759
Submitted	September 10, 2020
Last Modified	February 7, 2025
Applies to	ArcGIS Pro
Version found	2.6
Operating System	Windows OS
Operating System Version	10.0
Status	Will Not Be Addressed

Additional Information

This feature class has a renderer stored with its metadata at the geodatabase level which always get priority over the default behavior. This might have happened if you added the layer in ArcGIS Pro, changed its renderer to simple renderer and used a geoprocessing tool to store the result as a separate feature class. See the python script below to clear it out.```pythonimport arcpyimport xml.etree.ElementTree as ETfrom arcpy import metadata as md# Get the target item's Metadata object (update path to correct path)fc_path = r'C:\data\myFGDB.gdb\myFC'item_md = md.Metadata(fc_path)# Delete the layer file from item metadataif not item_md.isReadOnly: xml_content = item_md.xml root = ET.fromstring(xml_content) for esri in root.findall('Esri'): for dataProperties in esri.findall("DataProperties"): for layerFile in dataProperties.findall("LayerFile"): dataProperties.remove(layerFile) item_md.xml = ET.tostring(root);item_md.save()```

Workaround

Conduct the regular workflow of adding and applying the domains and subtypes to fields in a feature class (FC).
Copy this FC from within its file geodatabase (FGDB) in the Catalog tab (Right-click FC > Copy).
Paste the FC into the ArcGIS Pro project's default.gdb (Right-click FGDB > Paste).
This copied FC shows subtypes when added to the map's Contents.
Copy and paste the FC from the default.gdb to the original FGDB (it appears as FC_1).
FC_1 shows subtypes when added to the map's Contents.