Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
When you want to
transfer PARTsolutions attributes to PRO.FILE, then these have to be
specified in the configuration file ifprofile.cfg
in their own
section.
[AttributeMapping(is3d)]
Attr_Content_00 =PDMDocumentAttributes
Attr_Section_00 =PDMPROFILEATTR1
[PDMDocumentAttributes]
NFT_STK0="REREwr"
[PDMDocumentAttributes]
DOC_VSTL1="ERP_PDM_NUMBER"
DOC....="CADENAS_ATTR"
During checkin now the specified PARTsolutions fields are transferred to the assigned PRO.FILE documents and/or part fields.
However the datasets are only transferred from PARTsolutions at the first export.
Later changes are not exported anymore, because the part has been created and locked in PRO.FILE. EXCEPTION: If OVERWRITE_EXISTING_PARTFIELDS is set to 1, then fields of old PARTS (NFT_...) are overwritten.
Attribute mapping in the variable part master
Detailed information on this is found in the configuration file.
In the following you can see some important excerpts:
[AttributeMapping(is3d)] Attr_Content_00 =ProFileDocumentMapping Attr_Section_00 =ProFileDocumentMapping Attr_Content_01 =ProFilePartMapping Attr_Section_01 =ProFilePartMapping
[ProFileDocumentMapping]
;This section is for ProFile documents. Each Cadenas part is represented by a ProFile document
;in ProFile -> this mapping is for all Cadenas parts.
#:HELP;default; Example for a DocumentField.
;DOC_VSTL1=CNS TEST VAL
[ProFilePartMapping]
;This section is for ProFile parts. Only the RootDoc will be linked to a ProFile part and
;only if it has an ERP-Number -> this section is only for Cadenas RootDocs.
;Caution: If you want to use SML numbers the key used to set the "part-type"
;(e.g. to "Normteil") has to be the first one in this section.
#:HELP;default; Instructions:
;If you have to differ between fields with the same name (e.g. NFT_STK0) but different
;SML-numbers you can set the SML-number in the following way:
;<FieldName>{#1}=<value1>
;<FieldName>{#1}_BLOCKNUMBER=<SML-number1>
;<FieldName>{#2}=<value2>
;<FieldName>{#2}_BLOCKNUMBER=<SML-number2>
;CAUTION: The Format has to be exactly like in the example:
;<FieldName>{#<indexNumber>}=<value> . NO WHITESPACES !!!
Note | |
---|---|
In order for PartMapping to be enabled, there has to be assigned an ERP number in PARTdataManager. |
NFT_FLO0=?GetObject("iface.calcnameservice").start(0).Format("<ATTR(ERP_PDM_NUMBER)>").value()
Example with SML number and two fields with the same name:
NFT_FLO0=?GetObject("iface.calcnameservice").start(0).Format("<ATTR(ERP_PDM_NUMBER)>").value() NFT_STK0{#1}=Value1 NFT_STK0{#1}_BLOCKNUMBER=1531 NFT_STK0{#2}=Value2 NFT_STK0{#2}_BLOCKNUMBER=1764