Defining Microsoft Dynamics 365 Configuration using a JSON file

Overview

Microsoft Dynamics 365 configuration can be set up using a JSON file and uploaded from the Configuration > Bulk Operations > Configuration Data instead of doing it via the D365 Configurations screen.

Microsoft Dynamics 365 Parameters

The following parameters must be defined in the JSON file:

• name - the name of the configuration used in the extract configuration
• journalName - can be configured in two ways, depending on the journalNameMode as in the examples below:
  • Constant mode (CONSTANT):

  1
    "journalName": "ExampleConstantValue",
  2
    "journalNameMode": "CONSTANT"
  The provided journalName value (“ExampleConstantValue”) is used as a constant for all records exported to D365 using such configuration.
  • JLD-Mapped Mode (JLD_MAPPED):

  1
    "journalName": "ExampleJournalNameAttribute",
  2
    "journalNameMode": "JLD_MAPPED"
  The provided journalName value (“ExampleJournalNameAttribute”) will be used to derive the value from the Journal Line Definition attribute named “ExampleJournalNameAttribute”.
  Note that D365 Journal name attribute is a mandatory field. If the Journal Line Definition attribute holds empty values, the extracted D365 batch will be marked as Failed.

• accountDisplayValue - includes Journal attributes that are used to aggregate Journals and then sent as a batch to Microsoft Dynamics 365. These attributes must have the text format and must be also defined in Journal Line Definition. All of the attributes must have the matching configuration in Microsoft Dynamics 365.
  The Account attribute is required and must be on the first position.

• delimiter - a values separator that separates values of attributes from accountDisplayValue. We recommend the hyphen (-) as the separator.
• recurringIntegrationId - an ID for a data import job created in Microsoft Dynamics 365
• userDefinedAttributes - includes additional attributes selected by you. For each attribute, you need to define:
  • d365Label - a name of a column in the exported file that corresponds to the selected attribute from Journal Line Definition. Each label name must be unique, and it can contain only upper and lower-case letters, numbers, hyphens, underscores, and spaces.
  • jldAttribute - an attribute name taken from Journal Line Definition. The same attribute can be added multiple times but must be mapped to different D365 labels.
  • includedInBatchKey - an optional true/false flag affecting D365 batch key generation. When true, records with the same value for the selected attribute will be grouped under a single D365 batch key (i.e., Journal batch number) during D365 export.

Sample Microsoft Dynamics 365 configuration structure:

1
"d365Configurations": [
2
    {
3
        "name": "FynapseJournalConfiguration",
4
        "journalName": "FynapseJournals",
5
        "journalNameMode": "CONSTANT",
6
        "accountDisplayValue": [
7
            "customAccount"
8
        ],
9
        "delimiter": "-",
10
        "recurringIntegrationId": "866e83f1-066f-4942-9dad-38d7de42b8c0",
11
        "skipZeroAmountVoucherLines": false
12
    },
13
    {
14
        "name": "FynapseJournalMapped",
15
        "journalName": "customAccountingConfig",
16
        "journalNameMode": "JLD_MAPPED",
17
        "accountDisplayValue": [
18
            "customAccount"
19
        ],
20
        "delimiter": "-",
21
        "recurringIntegrationId": "86f56c8b-2b83-457d-89df-1171e3410e30",
22
        "skipZeroAmountVoucherLines": false,
23
        "userDefinedAttributes": [
24
            {
25
                "d365Label": "Core Date",
26
                "jldAttribute": "customCoreDate",
27
                "includedInBatchKey": true
28
            },
29
            {
30
                "d365Label": "Journal Type",
31
                "jldAttribute": "customJournalType",
32
                "includedInBatchKey": false
33
            }
34
]

Learn More

• Configuration Data