Field Mapping

Field mapping is leveraged to translate data from the API to a GlobalCapture process field. Not all fields returned from the API are necessary, and only those specified will carry into a capture process.

The o365 HTTP node automatically maps data to available Process Fields in GlobalCapture. By default, data is mapped from the Dynamics 365 response to a corresponding “header” process field. These are standard GlobalCapture process fields added to your workflow.

For example, a response from Business Central for and Account (GL Code) might look like:

{
    "id": "a2a5738a-44e3-ea11-bb43-000d3a2feca1",
    "number": "10000",
    "displayName": "BALANCE SHEET",
    "category": "Assets",
    "subCategory": "Assets",
    "blocked": false,
    "accountType": "Heading",
    "directPosting": false,
    "netChange": 0,
    "lastModifiedDateTime": "2020-08-21T00:24:15.327Z"
}

Any matching process field will be mapped automatically. So in the example above, a field called “displayName” will receive the value "BALANCE SHEET" without any additional configuration. The Business Central documentation clearly outlines available objects and what their expected response will look like.

Any response that might return more than one record will always map the first record only. If you need to map multiple records to a data set, as one might do when loading values into a list for example, leverage table fields for this task. The node supports the ability to automatically map and entire collection of results into this field type.

Note that when making requests to Dynamics, it might be beneficial to filter or restrict the response. A good rule of thumb is to request only what you need, not everything all at once.

It’s also important to schedule tasks to time intervals that are important to the job. For example, it would be ill-advised to have a workflow update your GL Account lists every 60 seconds. Placing that level of load on the Dynamics API’s is discouraged by Microsoft. Acceptable use limits are enforced by the Dynamics APIs and it’s very important design processes that will not spam the API’s or Microsoft will automatically block further requests for an indeterminate amount of time.

Handle collections of results with table fields

When you are requesting a collection of results, the Dynamics 365 node offers the ability to send that result to a table field. As with “header” fields, mapping happens automatically. As long as the table field has columns that match in name to the response from dynamics, the entire response will be retrieved and matching fields updated into rows of the table.

Simply providing a table field in the node configuration will indicate that data should be mapped to the table. It is acceptable to send a response that includes only a single filtered result to a table field as well.

In the node settings, specify a table field in the aptly named input:

Your column field names must match the response field names as noted above for standard “header” fields.