Following shall provide assistance for modelers to comply certain general conditions, in order for scripts to be able to run error-free.
An order number must be classified (CNSORDERNO), as the importer determines the part via the order number search.
CNSTYPECODE does not work here, because pipeline imports only run via CNSORDERNO (possibly changed yet, but not checked).
The column for the order number has to be a textual field. Numerical fields lead to problems with the classifications.
Value range fields: If the order number is dynamic, i.e. changes due to value range fields (yellow fields), the import only works partially.
The classifications are all written and displayed correctly, but the values that are added to the table (e.g. DESCRIPTION_SHORT, DESCRIPTION_LONG, TYPECODE) always overwrite each other so that the last value ends up in the table
Do not use the same part in several assemblies! (Only the first would get the classification.)
-> Connection points have to be unique. This is only possible based on independent projects.
Do not use the same part several times in an assembly!
-> In this case, it is better to create a separate project from the geometric copy (with different connection point names
If the connection points have the same name, only the first subpart will get classification data.
Do not use the same part as independent part AND within an assembly!
-> In this case, it is better to create a separate project (with different connection point names) from the geometric copy.
Ideally, the NB in subparts of assemblies should be unique and not translatable.
If the sub-assembly also contains an order number, it is unique . As a rule, however, subparts do not contain an order number.
Modelers and Electro-Team must cooperate closely in order to avoid double work!
Some variable columns have to be filled manually, others by scripting.
