powered by CADENAS

Manual

Manual

4.24.5.6. Tabbed pages Standard name , Standard name (short) , BOM name

[Important] Important

The file name for the exported CAD document must be absolutely unique.

The whole CAD administration including the specification of the name rule is performed via the CAD configuration file under $CADENAS_SETUP/if<cad name>.cfg.

Detailed information on the CAD administration in general is found under Chapter 2, PARTsolutions - CAD Integration - Administration. Detailed information on the creation of the file name in particular is found under Section 2.2.2, “Set file name ("FileName" key) and pool path ("poolpath" key) ”.

By default, on the tabbed pages Standard name, Standard name (short) and BOM name, NO entries are performed! Then in PARTdataManager, in the 3D view, the standard NB and in the table docking window the standard LINA is displayed and the setting under $CADENAS_SETUP/if<cad name>.cfg is used unchanged.

Part name

Part name

If entries are performed on the tabbed pages Standard name, Standard name (short) and BOM name then these will change the NB! This again affects the setting under $CADENAS_SETUP/if<cad name>.cfg and so the CAD file name!!

You can find the setting options both in PARTlinkManager and in PARTadmin. The syntax is identical.

  • PARTlinkManager -> Extras menu -> Configure ERP environment -> tabbed pages Standard name, Standard name (short) and BOM name

    Role-independently

  • PARTadmin -> Roles category-> Standard name, Standard name (short) and BOM name tabbed pages

    Role-dependently

If standard configuration options should not suffice, there are further extra options available::

  • Change NB according to project

    If the NB is part of the naming rule the NB can be adjusted according to projects. In any case the basic rule is entered in the dialog area of the respective tabbed page.

    See Section 4.25.7.7.1, “Change standard descriptions according to project ”.

  • vbs scripting

    If the options in the entry field do not suffice, you can generate a reference to a vbs script and work with complex conditions.

    The call of the external script happens with NB=TSCRIPT('nb.ruletable','$CALCED_ROW.','$NB.').

    Also see Section 6.1.6.1, “Example 1”.