|
Mapping |
Scroll |
It is recommended to synchronize the configuration before the mapping.
In the Setup tab, choose Synchronize Configuration to load the Category Definitions and Case Definitions from Therefore™. This will ensure that all field numbers and category numbers are up to date when doing the mapping. If you get a Web Service Call failed error, please check if HttpClient Requests are enabled in the extension settings.
In the Setup tab, choose Mappings to add new mappings or change existing ones.
|
Note: By default, there are no mappings which means that the connector won't do anything. The Therefore™ Drop Zone for storing and viewing Therefore™ documents will only be visible for mapped Microsoft Dynamics 365 Business Central Tables. |
Click on New to create a new mapping; all changes are automatically saved and will also be effective immediately.
The BC Table entry needs to match a table in Business Central and the Category No. needs to match the category number in Therefore™.
Both can be conveniently selected using the drop-down menu. There is no need to look up IDs manually. Optionally, a Subcategory Field No. can also be used if such a keyword field is used in Therefore™ for a sub-category. In this example, it is Document Type with FieldNo. 1410.
When saving a document using the Drop Zone, a keyword value can be chosen in the Add Document dialog. Using different Subcategory Field numbers allows multiple mappings to be active for the same Microsoft Dynamics 365 Business Central table.
There are different mapping types to choose from:
1. Drag & Drop
This mapping type defines in which Therefore™ Category a document should be stored and what index data it should contain. This mapping is executed when adding a document via 'Drag & Drop' to the 'Drop Zone'.
It is possible to have multiple 'Drag & Drop' mappings. For example, this is useful for saving documents in different Therefore™ Categories.
2. Backend
This mapping type generates a document based on the selected report and saves it to Therefore™.
It is similar to Drag & Drop mappings: both index data and category can be specified.
This mapping will be executed on a certain trigger that depends on the Business Central page. For example, this can be posting or printing.
There can only be a single 'Backend' mapping or 'Drag & Drop / Backend' mapping active at the same time.
3. Drag & Drop / Backend
This mapping is a combination of the 'Drag & Drop' mapping and the 'Backend' mapping. It includes a report as well as the DropZone.
4. Late Linking
This mapping defines how Late Document Linking should search for documents in Therefore™.
If index data should be automatically added as well the Microsoft Dynamics 365 Business Central columns need to be mapped to Therefore™ index data fields.
The three dots button ("...") can be used to search such a column:
To complete the new index data mapping, a Therefore™ index data field needs to be selected as well:
Macros can be used as well if Data From is set to Text:
The following macros are supported:
[CURRENT_DATE] |
Stores the current date to the selected Therefore™ index data field |
[USER_ID] |
Stores the currently logged on Therefore™ user to the selected Therefore™ index field |
[AH_FILENAME] |
Stores the name of the file that is about to be saved to the selected Therefore™ index field |
[AH_ADDITIONAL_INFO] |
Stores the value of the 'Additional Info' text field in the 'Add document' dialog to the selected Therefore™ index field |
Finally, please make sure that the category mapping is active.
Newly created mappings are not activated by default.
