The entry is saved and does not need to be re-entered for a new import of the same PDT.

Products are not loaded automatically after a change. Load products must be executed after the entry.

Do not use a search [Do not use search] via the new button catalog resolve [Resolve Catalog] . As long as the order number and there are no variants, it is not needed. In the case of yellow fields (value ranges), the function a resolution of the variants can be started. Order numbers of the Variants end up in a cache ( $CADENAS_USER/pdt_import/cache.json ), which is then used to identify the correct lines becomes. As long as the catalog does not change, this is only once necessary.

Variant mode (classifications are valid for the entire project) [Variant mode (classifications are valid for the whole project)] is mapped via the PDT file and a CNS_CONDITION column. If classifications are to apply to the entire project file ("entire" means for all values of the value range variables), a CNS_CONDITION with the value "empty" must be set (possible in all relevant tables).

CNS_CONDITION

Combining attributes [Combine attributes] is completely unnecessary. If you want fields with algorithms(in the example below it is not an algorithm, is it?), the recommended way is to enter them manually in the table and use square brackets in the PDT to instruct the importer to refer to the corresponding column [COLUMN NAME] -> Classification refers to the table column COLUMN NAME.

Remove old classifications during import: This can be mapped after loading the products using the new Delete classifications button. All classifications with an instance name beginning with "PDT_" are deleted.

Process parametrically [Parametric processing]: Not applicable and is controlled via the CNS_CONDITION column of the Connection Point Information Excel table.

The Debugging information is stored after each import under $CADENAS_USER/pdt_import loaded.

In addition to the EClass property line, the variable name line is now also processed. While the first should be a unique ID (if it occurs twice, the first is regarded as the German and the second as the English translation of a field), the second should contain an attribute name so that it can be mapped directly to an attribute of a class. The mapping can be overridden in the configuration file. Ultimately, however, it would be optimal to have as much correct mapping as possible in the PDT template.

Example

If 2 assemblies share the same subparts, already classified connection points are recognized and updated with the new values of the current import. If these are to have different values, assembly connection points must be used, as different values for points would only be possible in this case if they could be distinguished for their respective assembly via the CNS_CONDITION.

No specific tables need to be available to carry out an import. For example, an import can be made that imports only CP or only accessories.