Be.Smart ERP Connector
(EN) Consultant Manual
(EN) Consultant Manual
  • Be.Smart ERP Connector Consultant Manual
  • Abbreviations used
  • Home
  • Purpose of the product
  • Technical solution
    • Data Interface
    • Autodesk Vault
    • Basic types of jobs and their origin
  • Configuration
    • EC configuration (central)
      • Main Card
      • Property Values tab
        • Tab < entity>
    • EC local configuration
    • Logging in
      • Logging to the local station
      • Logging in DI
    • Reverse logging
      • Description of the reverse logging process
    • FLAGs (additional flags in std Vault configuration)
      • List of symptoms
  • Commands and Features in Vault Explorer
    • Attach to already existing purchased item
    • Apply item security to files
    • Create Raw material BOM rows
    • Send to DI (Send to Data interface)
    • Data interface browser
      • Functions
  • Export
    • Item breakdown
      • BOM loading method
      • Transfer MJ
    • Atypical requirements
  • Imports
    • Processing of external requests for transfer to Vault (from version 2019 inclusive)
      • The procedure for processing the Arkance.Import initialization job:
    • PreProcess sample
    • Imports of entities
      • Entity identification by ERP system
      • Import items
      • Importing applications
      • Import folder
      • Importing a change command
      • Import schedules
  • Recommended commissioning procedure
    • DI commissioning
    • Mapping fields
  • Castomization (ec addons)
  • Attachments
    • Job types - complete list
    • Configuration type Global/Workgroup
Powered by GitBook
On this page

Was this helpful?

  1. Imports
  2. Imports of entities

Import folder

In the EcENTITY table, one field must be mapped to a property with the system name "FolderPath" (full folder name).

up to and including the 2018 version:

In addition to the properties in the EcENTITY table, you must write an entry to EcLINK that references EcENTITY.id using the EcLINK.ent_id field.

Example of values:

  • EcENTITY

    • name = 'Project XYZ'

    • ent_class_id = 'FLDR'

  • EcLINK

    • object_name = '$/Projects/Power plant/Project XYZ' (i.e. the full folder name)

    • link_type = 1 (i.e. FullClientCompose)

    • ent_id = (id value in the EcENTITY table)

In addition, if the imported folder is required to be structured according to a Vault template, an additional EcLINK entry must be created:

  • ent_id = (id value in the EcENTITY table)

  • link_type = 2 (i.e. FullClientAcrContents)

  • object_name = '$/Templates/Projects/Power plant' (i.e. the full name of the source folder for cloning)

If a folder of type library is to be imported, EcENTITY.base_uom='LIBRARY' must be set.

PreviousImporting applicationsNextImporting a change command

Last updated 11 months ago

Was this helpful?