Add Mapping for Missing or Custom Dataset and Named Reference Types

If your Teamcenter business model includes custom dataset types such as ProEDataset_asm or ProEDataset_prt for Creo assembly and part files, you’ll need to update your configuration to ensure proper mapping and downstream compatibility with HyperMesh.

Update the <FailingOrder> section by adding the ProE keyword to the list.
This is a reserved type recognized by the HyperMesh API and enables the correct association with your Creo files. For the full list of supported values, refer to Supported UDMElementType Values.
```
<FailingOrder>
    <Value>ProE</Value>
    <Value>CATIA V5</Value>
    <Value>JT</Value>
    <Value>Unigraphics</Value>
</FailingOrder>
```

Add custom dataset mapping to <PLMXMLElementToUDMContentDefinitions> by inserting the following blocks to define how your custom datasets should be interpreted by HyperMesh.

<PLMXMLElementToUDMContentDefinition>
    <PLMXMLElement>DataSet</PLMXMLElement>
    <PLMXMLElementType>ProEDataset_asm</PLMXMLElementType>
    <UDMContentDefinitionType>UDMRepPartCad</UDMContentDefinitionType>
    <UDMIsPrototype/>
    <UDMElementType/>
    <UDMBindingClass>com.altair.hwec.udm.base.RepresentationPartCType</UDMBindingClass>
</PLMXMLElementToUDMContentDefinition>

<PLMXMLElementToUDMContentDefinition>
    <PLMXMLElement>DataSet</PLMXMLElement>
    <PLMXMLElementType>ProEDataset_prt</PLMXMLElementType>
    <UDMContentDefinitionType>UDMRepPartCad</UDMContentDefinitionType>
    <UDMIsPrototype/>
    <UDMElementType/>
    <UDMBindingClass>com.altair.hwec.udm.base.RepresentationPartCType</UDMBindingClass>
</PLMXMLElementToUDMContentDefinition>

Note: If you're defining a CAE dataset, replace UDMRepPartCad with UDMRepPartMesh.

If your datasets reference external files (.prt, .asm, and so on), include the following named reference mappings:
```
<PLMXMLElementToUDMContentDefinition>
    <PLMXMLElement>ExternalFile</PLMXMLElement>
    <PLMXMLElementType>prt</PLMXMLElementType>
    <UDMContentDefinitionType>UDMDSFileCAD</UDMContentDefinitionType>
    <UDMElementType>ProE</UDMElementType>
    <UDMBindingClass>com.altair.hwec.udm.base.DataSourceFileCType</UDMBindingClass>
</PLMXMLElementToUDMContentDefinition>
```
```
<PLMXMLElementToUDMContentDefinition>
    <PLMXMLElement>ExternalFile</PLMXMLElement>
    <PLMXMLElementType>asm</PLMXMLElementType>
    <UDMContentDefinitionType>UDMDSFileCAD</UDMContentDefinitionType>
    <UDMElementType>ProE</UDMElementType>
    <UDMBindingClass>com.altair.hwec.udm.base.DataSourceFileCType</UDMBindingClass>
</PLMXMLElementToUDMContentDefinition>
```
Note: Use UDMDSFileCAD for CAD content and UDMDSFileMesh for CAE/mesh data. Match this with the UDMRepPartCad or UDMRepPartMesh types you’ve defined above.

Supported UDMELEMENTType Values

For UDMDSFileCAD

Acis, Aveva, CATIA, CATIA V4, CATIA V5, CATIA V6, DXF, ECAD, FEMAP, FORAN, HyperMesh, HyperForm, HMAscii, IFC, Iges, Inspire, Intergraph, Inventor, JT, Parasolid, PDGS, Pdgs, ProE, Pro/E, Rhino, SolidWorks, Step, STEP AP242 XML, STL, Tribon, Unigraphics, VDAFS.

For UDMDSFileMesh

Abaqus, Ansys, Ansa, HMAscii, HyperForm, HyperMesh, Ls-Dyna, Ls-Dyna Seq, Moldflow, Nastran, OptiStruct, Pamcrash, Pamcrash 2G, Permas, Radioss Block, Radioss Bulk, Stl.
After editing the XML file, validate the XML file structure.
1. Open the file in an internet browser (Chrome, Edge, Firefox, and so on).
2. Ensure the structure loads without errors and shows collapsible nodes (confirming valid XML syntax).
  This helps catch syntax issues before runtime errors occur in HyperMesh or other consuming applications.