 |
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 has to be classified (CNSORDERNO), because the importer detects the part via 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, meaning changes by value range fields (yellow fields), the import will work only partly.
In fact the classifications are correctly written and displayed, however, those value which are entered into the table (e.g. DESCRIPTION_SHORT, DESCRIPTION_LONG, TYPECODE) overwrite each other so that the last value will be 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 an independent project should be created from the geometrical copy (with other 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 an independent project should be created from the geometrical copy (with other connection point names).
Ideally, the NB in subparts of assemblies should be unique and not translatable.
If the NB includes an order number, it is unique. However, subparts do no have an order number normally.
Modelers and Electro-Team must cooperate closely in order to avoid double work!
Some variable columns have to be filled manually, others by scripting.
