Excel to GDB with Domains, Fieldnames and Field Alias

Hello @abnan0001

There seems to be some data quality issues with the coded domains values from the Excel dataset that causes the third workspace to fail.

First, there are non-printing characters at the end of some Code and Description values that causes the geodatabase writer error. See the Neumanns Agama feature as an example. You can use a StringReplacer to replace \x{00A0} with nothing to remove this character, or clean up the Excel dataset to remove this character.

Second, there are duplicate coded domain values which is not allowed. Cheloniidae and Viperidae appears twice for the family_name coded domain. You need to remove these duplicate values either in the workspace with a DuplicateFilter or in the Excel dataset.

Lastly, there is no data type defined for the HCP_SR_21 coded domain. The Field_type attribute value is double, but there is no conditional rule in AttributeCreator_11 to map a Field_type value of double to an fme_data_type value. The correct field type for this coded domain should also be long/short integer instead of double.

If you fix all three of these issues, the Geodatabase writer should successfully write out the coded domain values in the output geodatabase. I hope this information helps.

@debbiatsafe 

Thank You So Much 

It is working perfectly and I have tested with some other data, It Works Fine..

Wondering of Sub-Type..

I may need your suggestion and support in Sub-type

Is there a possibility that FME form software Supports building Sub-types within the same Workspace with the same logic applied for domains

Thank You

Hello @abnan0001 

Please note, there is a bug tracked as FMEENGINE-81757 affecting the creation of subtypes in FME 2023.1 and 2023.2. This bug has been fixed in FME 2024.0. If you cannot upgrade FME, you can use a geodatabase template as demonstrated in How to Use an Esri Template to write feature classes with subtypes, which is the recommended method for creating subtypes and domains.

In general, you cannot use the same workspace as-is to create subtypes. You will need to modify the existing workspace logic to produce a similar workflow for writing subtypes.

This is because the syntax is slightly different compared to a domain. For example, this is the string required in attribute{n}.native_data_type for a coded domain:

coded_domain(<domainName>:<domainFieldType>:<code1>:<encodedCode1Description>:<code2>:<encodedCode2Description>)

For a coded subtype, the string in attribute{n}.native_data_type should be:

subtype_codes(<code1>:<encodedCode1Description>:<code2>:<encodedCode2Description>)

There is a different key word at the beginning, and coded subtypes do not require the subtype name and subtype field type.

Hello @abnan0001 

Unfortunately, sample workspaces for creating subtypes using this method are not available as this is not the recommended way to create domains and subtypes for geodatabase writing anymore. As you have noted, the workspace you are using to create domains is a very complex workflow.

The recommended method to create subtypes and domains is using an XML geodatabase template, as it is a simple to configure.

I would highly recommend taking a look at our article on How to Use An Esri template Geodatabase for a much simpler way of creating subtypes and domains for geodatabase.