ECM Transfer/Update Document Definitions
The transfer functionality is used to transfer documents from a source library / storage to one or more target libraries / storages where you can enrich metadata in the target library / storage when storing / archiving the transferred document. For this purpose, EASY for Dynamics 365 BC provides the capability of automatically enriching during transfer the metadata of imported documents from the metadata of exported documents of the same process. The enhanced information is available in Microsoft Dynamics 365 Business Central, i.e. there is no postback to the source library / storage of the document. However, the copy in the target library / storage also contains the enriched metadata.
A transfer definition defines in detail which data will be transferred from one ECM library / storage to another when transferring a document, and how this occurs in terms of time. You have to create a transfer definition for each ECM library / storage to which data is transferred.
Example
Imported documents from archives containing scanned documents are usually information-poor. Scanned documents that, for example, only contain a barcode as an index term can be enriched with additional metadata from the process through a transfer. The transferred documents can then be found in Microsoft Dynamics 365 Business Central and EASY Archive / SharePoint not just with the barcode, but also with other search terms.
Unlike a document definition, the Document journal line and Document entry tables are stored as fixed base tables in a transfer definition. Microsoft Dynamics 365 Business Central is able to transfer only these fields directly to the desired metadata fields in the target library / storage.
Transfer/Update document definition actions
Action |
Meaning |
Function |
|
Determine next transfer/update time |
This action determines the next transfer/update time, taking the configuration in the selected Transfer/Update document definition into consideration. |
Scan lines, and prepare Transfer/Update |
This action scans the document lines, preparing records that may have been found for transfer or an update, i.e., queue entries are generated for these document lines. |
Copy definition* |
Copies setup (header and rows) of a document definition to be selected to this definition. When creating a new definition and no other field is populated except for the code, the "Including header" option must be enabled, because otherwise values cannot be imported. This is because the "Table ID", "ECM server code", and "ECM repository" fields are validated and, if necessary, a new error message appears..
|
Copy definition to other units |
This function copies a document definition(s) to any number of other units. Copying Setup Data to Other Clients |
Refresh ECM Repository/ library reference and content type |
This function refreshes the ECM Repository / Library reference field . |
Validate rows |
This function targets the rows of a document definition. The rows are validated and, if necessary, detected misconfigurations are output in a message. |
Import/export ** |
|
Import ECM document definitions |
Imports document definitions that have previously been exported in XML file format from another database. This ensures transfer from legacy systems to new systems, or from test systems to production systems. |
Export all ECM document definitions |
Exports all document definitions to an XML file. |
Export selected ECM document definitions |
Exports selected document definitions to an XML file. |
Import ECM document definitions (C/SIDE format) |
Imports document definitions that have been exported in XML file format from a C/SIDE implementation. This enables continued operation of the interface when switching from C/SIDE implementations (EASY for Dynamics NAV to Dynamics 365 Business Central version 14) to AL Code in Dynamics 365 Business Central. This data port automatically performs a transformation to the new data model. |
* This action is only available in tab view
** This action is only available in list view