When using TC11.4 or newer AND NX12.0.1 or newer, editing the CMM Inspection PAX files doesn't work.
Processing C:\siemens\nx\CMM_INSPECTION\templates\nxdm_ugs_inspection_templates.pax for File New Templates
Note: Validation of the <RelationType> value: 'master' is skipped for template: Template Name DMIS General Setup11, Filename %UGMGR=V3.2 PH=CAU1dL45pEFflA PRH=CNU1dL45pEFflA PN=insp_general_assy_metric PRN=A RT="has shape" AT="UG master part file" , application type InspectionTemplate.
Error in template validation: The part specified in the template is of wrong type.
Please use a template part which is created from the out-of-box template part.
Solution
When using TC11.4 or newer AND NX12.0.1 or newer, NX CMM Inspection uses a new Business Object Type (ItemType) for the inspection setups. This was done so that the DMIS output files can be stored in 'Activities' in 'Part Planner'. When the customer went to TC12 from TC11, NX CMM Inspection started using the new Business Object type. The OOTB Pax files have entries in them for both the old and new business objects. But only the proper entries will be used.
The original Business Object type ( <ItemTYpe> ) is "Mfg0CMMInspect". You can see this in the nxdm_ugs_inspection_templates.pax file as shown here:
<PaletteEntry id="d1">
<References/>
<Presentation name="DMIS General Setup11" description="NX CMM Inspection DMIS General Setup">
<PreviewImage type="UGPart" location="${UGII_INSPECTION_TEMPLATE_PART_METRIC_DIR}inspection_setup.jpg"/>
</Presentation>
<ObjectData class="InspectionTemplate">
<Filename>@DB/insp_general_assy_metric/A</Filename>
<Configuration>${UGII_INSPECTION_CONFIG_DIR}inspection_teamcenter_general.dat</Configuration>
<LibraryClassPath>SETUP_TEMPLATE;GENERAL</LibraryClassPath>
<Units>Metric</Units>
<UsesMasterModel>Yes</UsesMasterModel>
<ItemType>
Mfg0CMMInspect</ItemType>
<RelationType>master</RelationType>
</ObjectData>
</PaletteEntry>
The new Business Object type is "Mfg0CMMInspMEOP". Here is an example. There are duplicate pax file entries with a different PaletteEntry id and the new ItemType at the bottom of the pax file.
<PaletteEntry id="d101">
<References/>
<Presentation name="DMIS General Setup" description="NX CMM Inspection DMIS General Setup">
<PreviewImage type="UGPart" location="${UGII_INSPECTION_TEMPLATE_PART_METRIC_DIR}inspection_setup.jpg"/>
</Presentation>
<ObjectData class="InspectionTemplate">
<Filename>@DB/insp_general_assy_metric/A</Filename>
<Configuration>${UGII_INSPECTION_CONFIG_DIR}inspection_teamcenter_general.dat</Configuration>
<LibraryClassPath>SETUP_TEMPLATE;GENERAL</LibraryClassPath>
<Units>Metric</Units>
<UsesMasterModel>Yes</UsesMasterModel>
<ItemType>
Mfg0CMMInspMEOP</ItemType>
<RelationType>master</RelationType>
</ObjectData>
</PaletteEntry>
The OOTB pax file contains both the old and new entries. The new entries are at the bottom. Only the correct entries will be used by the File->New Tab. So both sets of entries can exist in the PAX file. Originally the customers setup would have used the pax file entries with "Mfg0CMMInspect" at the top of the file and it would have ignored the new ones with Mfg0CMMInspMEOP at the bottom.
Now that they have moved to TC12, their setup will use the pax file entries at the bottom of the file with "Mfg0CMMInspMEOP" and it will ignore the old ones with "Mfg0CMMInspect" at the top of the file. So if the old entries are edited, the File->New tab will not see that, because those entries will now be ignored. The new pax file entries with "Mfg0CMMInspMEOP" must be edited. Those edits will be seen in the File->New tab.
If their imported pax file has both the new and old entries, they can edit the new entries to match what they want displayed.
Another option would be to delete the new entries and then edit the old entries to change the <ItemType> to Mfg0CMMInspMEOP.
Hardware/Software Configuration
Platform: INTEL
OS: windows
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V1880
Function: FILE_NEW
Ref: 002-8016466