Eplan Platform API
EPLAN API / API Reference / Actions / XMImportDCArticleDataAction
In This Topic
    In This Topic
     Imports a data configuration file into an existing EPLAN Article database.

    Parameter Description
    path of data configuration file
    defines the progress title (optional)
    0==only create new objects, 1==only update objects, 2==create new and update objects (optional)
     If not entered, objects are updated and if new objects are in the list, a question dialog comes up, if new objects should be created.
    0 or 1, if 1 objects are identified by name instead of id (optional)
     If not entered, objects are identified by Object-Id.
     These 2 modes are meant for different workflows/use-cases:
     If you export data from the parts-management, change them and import them into the same parts database, then
     identifying the objects by Object-Id is the right mechanism for identification and it is possible to change
     the identifying name of the objects (for example the part number)
     If you want to import data from a different data source, for example a file generated from a connection to a ERP-System,
     you usually don't have an object-id of EPLAN. In this case, use the identifying name to import the data.
     If imported by name, some part of the object-id must be defined nevertheless in the first column - the type of the object,
     to define if the data contains for example to a part, an address or a accessory list.
     The supported main types are:
     117 for part
     156 for drilling pattern
     157 for connection point pattern
     213 for accessory list
     226 for accessory placement
     135 for address
     The import does not only support main types, but their sub-types, too. Since they have no identifying name but are
     identified as a sub-object of the main-object, they have to be defined in the second column in a format "99 (117:99/1)",
     where the first 99 means the sub-type and in brackets is the relation: Containing to a main object, the relation and its index.
     So "99 (117:99/1)" means it is a function template (first 99), and is related to a part (117) where is is the first index
     into the parts function templates. Sub-objects must follow main-objects in the imported file.
     Valid sub-types are:
     For a part:
     99 for a function template
     85 for a module/assembly position
     224 for drilling patterns
     215 for accessory
     242 for safety related values
     For a drilling pattern:
     158 for a cut-out
     For a connection point pattern:
     159 for a connection point
     For an accessory list:
     214 for an accessory list entry
     For an accessory placement:
     227 for an accessory placement entry

     This allows the properties of articles to be changed.
     The  data configuration file can e.g. generated by the menu item "Utilities->Edit properties externally->Export functions…"

            XMImportDCArticleDataAction /DataConfigurationFile:c:\\EPLAN\\DataCfgFile.edc