I used the FeatureReader to read all feature classes in a file geodatabase and dynamically update the same feature classes in a different geodatabase. Some of the feature classes use attribute domains with code values different than the descriptions. This causes failures in the update. For example, a feature class has an attribute Country defined as integer, and its domain Description is country names (text). Behaving like ArcGIS, the FeatureReader reads the Description text values and write to the destination feature class, which has the same Country defined as integer. The data type mismatch between the FeatureReader output and the destination caused the update to fail. As it is very typical in ArcGIS for a domain to have different code and descriptions values and therefore I would think FME should have been able to handle this gracefully, but I don’t see a workaround option with the FeatureReader. I am at FME Form 2022.2.2. I hope I don’t have to use those Customers or Hub GDB Domain transformers to work around this.
When reading Esri Geodatabase formats, you can click on the Parameters button and there is an option to Resolve Domains.
Note, you will need to be using the Esri File Geodatabase format, not the open API format.
As per the documentation,
Specifies whether or not to resolve the domain code found in feature classes and tables into the domain value.
This means that when an attribute of a feature has a coded value domain associated with it, another attribute will also be added that represents the textual description of the coded attribute. The new attribute will be <attribute-name>_resolved, where <attribute-name> is the name of the attribute containing the code.