Parts administrated in PARTsolutions are identified by the MIdent by default, when processing the Document scan.

As of V9.08 there is a new option: Parts administrated in PARTsolutions, which do not have a MIdent - because they were imported by the Classimporter for example -, can be identified by the value of a user defined CAD attribute (the ERP number for example).^[160]

In the following the background is explained using an example:

Initial situation in CAD system (here exemplified by an Inventor assembly):

The user defined attribute "ERP" contains the ERP number.

Initial situation in PARTsolutions:

A part imported in PARTsolutions by the Classimporter for example has no MIdent, but an ERP number.

In order to map this information (LinkDB attribute and CAD attribute), in PARTadmin, make the following settings:

In the configuration file under $CADENAS_SETUP/docscan.cfg, in the section ImportOptions, in the key ModelMappingFilterList, add the value ErpAttributeFilter comma separated in addition. (Per default there is only the value MIdentFilter.)

[ImportOptions] 
ModelMappingFilterList=MIdentFilter,ErpAttributeFilter

This value ErpAttributeFilter is the name of another config section:

In this section, set the following keys:

[ErpAttributeFilter] 
FilterClass=ErpAttributeFilter 
ColumnName=ERP_PDM_NUMBER 
Attribute=ColumnName

At first the CAD attribute is queried at the model, if it is not found there, then at the document.

When you execute the Document scan in PARTdataManager for the respective assembly now, then parts existing in the LinkDB are identified.