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. Attachments

Configuration type Global/Workgroup

PreviousJob types - complete list

Last updated 2 years ago

Was this helpful?

since version 26.0.4.0 it is possible to set the validity of a configuration in a replicated environment - the configuration types are:

  • Global one for all workgroups (default)

  • Workgroup independent of other workgroups

settings are available only in a replicated environment or when the Workgroup configuration type is active:

if the Workgroup configuration type is used (a different configuration from other Workgroups in the replicated environment), this status is indicated by underlining the entire dialog box.

Along with the introduction of this option, the internal names (OptionName) that EC uses to store the configuration have changed - SQL table [storage].[dbo].[KnowledgeOption]

Original condition:

New condition:

The EC decides when reading the cfg whether to use the original or the new OptionName - i.e. the "new" or the "old" configuration. An entry is used for this decision where OptionName='ErpCnn2g. LocalWkgCfg#< local workgroup label> '. (example: ErpCnn2g. LocalWkgCfg#WG1)

If this record exists, it will use the new OptionName (have the '#' character in the name). Old names are left in the db for the possibility to use them for recovery.

Remove them from the db with the command:

DELETE FROM KnowledgeOption WHERE OptionName LIKE 'ERP%' AND CHARINDEX('#', OptionName)=0

If DiagMode=True is set, EC also writes the configuration to the local folder of the machine on which the cfg save was called.

In connection with the OptionName change, the names of locally written files were also changed to better correspond with the OptionName and the contents of the files were usable for restoring values in the db (Copy/Paste):

each set of files has a single prefix (=time)