This document is intended for technical staff creating imports to Signifikant Platform and describes the Signifikant Simplified XML import format.
...
When the first step of the import is started, Signifikant Platform will look in the export directory specified in the config file and match the folders found according to the regex in the config file. The information found will be transformed and placed in the import directory along with a .lis file specifying the content.
| Info | ||
|---|---|---|
| ||
A good practice is to use a naming convention for import folders based on <source>_<year>-<month>-<day>_<time>. E.g. “ERP_2020-02-01_103121”. Note the date format with year-month-day. This helps sorting the folders in windows explorer making it easy to find the latest export. |
Task scheduler will import folders in one task based on alphabetical sorting, so ensure to use a convesion that works with this sorting
The second step, the actual import, will look in the import directory and match he folders with the regex in the config file and the actual files listed in the .lis file to determine what to import. When the second step of the import is completed, Signifikant Platform will place a status.xml file in the import directory.
...
* The persistent-identity is the only attribute that is required in the import file. Often the identity, persistent-identity and number are the same, but there are use cases where these have different values.
| Info | ||
|---|---|---|
| ||
The persistentID has to be unique per type of information and no duplicates may exist. E.g. there may only be one part with the same persistentID. If persistentID is not unique the import engine will get confused and unexpected results may occur. |
Specifications
You can add an arbitrary number of additional attributes to most data types in the Signifikant information model. During import, you provide their values by using the Specifications tag which takes key/value pairs (called type and value).
...
Each text may be defined by a persistent id which can be referred from all other exports. Each text contains all translations for that text with language defined using ISO 639-1 alternatively ISO 639-1 and ISO 3166.
A text with language "" is considered being invariant, the same for all languages.
...