Be.Smart ERP Connector
(EN) ERP Connector
(EN) ERP Connector
  • ℹ️What is ERP Connector?
  • ⚙️System Requirements
  • 🔑Installation & Activation Guide
  • 🆕What's New
    • Versions 30.1.0.6, 29.3.0.5, 28.8.0.5 & 27.14.0.5
    • Versions 30.0.0.3, 29.2.1.2, 28.7.3.3 & 27.13.0.5
    • Versions 28.7.1.1, 27.13.0.1
    • Versions 29.2.1.0, 28.7.1.0, 27.13.0.0
    • Versions 29.1.0.0, 28.6.0.0, 27.12.0.0
    • Versions 29.0.0.1 & 28.5.1.1
  • Data Interface - Reference Manual
    • Abbreviations
    • Data interface
      • Data tables, relations
        • Table EcENTITY
        • Table EcASSOC
        • Table EcLINK
        • Table EcLOG
        • Stored procedure EcWriteEntity
    • Exporting data from a Vault
      • Properties / Attributes
      • Associations
      • Links
      • Reading data from data interface
        • Workflow sample
        • Another samples
    • Importing data into a Vault
      • Mandatory EcENTITY table fields
      • Default values
      • LifeCycle States
      • Writing data into data interface
        • Using SQL Stored Procedure
          • Example #1 – insert single EcENTITY record
          • Example #2 – insert two associated EcENTITY records
        • Using SQL syntax
        • Using SQL Management Studio
    • SQL views
      • ERP data displayed dynamically in VE Tab
        • SQL view definition sample:
      • ERP synchronized enums
    • Logging
    • Using thumbnail image data
Powered by GitBook
On this page

Was this helpful?

  1. Data Interface - Reference Manual
  2. SQL views

ERP synchronized enums

Selected Vault Property values (enums) can be periodically updated from an external source (eg. ERP). This ec function is based on the following rules:

  • up-to-date (ERP) values are available as first column table in a SQL view

  • the name for the SQL view:

    1. pattern: EcPDV_<VaultPropertyDefinitionId>

    2. example: EcPDV_56

  • the first field data type must comply with Vault property data type (string or numeric) Synchronization can be configured:

  • sync time pattern (when the function is activated)

  • enable the command to manually activate synchronization

  • remove obsolete value from Vault property definition (the value is not defined by ERP anymore)

to explain: on Vault entities having the obsolete value, this will cause “non compliant” property value status; if obsolete value is detected, Arkance.AdminRequest job is created (this job will never be processed by any JobProcessor - it waits in queue for admin to take action and manually remove this job from a queue)

  • sort value - if selected, values are sorted; on the contrary this will invoke reindexing of Vault properties and slows down the Vault server

PreviousSQL view definition sample:NextLogging

Last updated 12 months ago

Was this helpful?