Resources
Help & Support ↗ Lucanet Learning Space ↗
Documentation
Getting Started
Global Functions
Lucanet Lume
Administration
Data Hub
Integrations
Microsoft Dynamics 365 Business Central Beta
Microsoft Dynamics 365 Business Central (JDBC)
Microsoft Dynamics 365 Business Central (OData)
SAP S/4HANA (RFC)
Managing Connections
Managing Source Datasets
Importing Data
Consolidation & Financial Planning
Lease Accounting
Extended Planning & Analysis (xP&A)
ESG Reporting
Disclosure Management
XBRL Tagger
Tax Compliance & Reporting
Banking & Cash Management
Data Collection
Glossary

Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

Overview

The Microsoft Dynamics 365 Business Central (OData) integration in Data Hub extracts data from Microsoft Dynamics 365 Business Central through OData v4 and writes it into the Lucanet Data Lake as raw Parquet datasets. From the Data Lake, the data is available for further processing on the Lucanet CFO Solution Platform.

This page describes the technical details and the prerequisites of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub, every step from creating the connection to starting the import, the connection settings, every option of the source dataset configuration, example configurations, a configuration checklist, and the release notes.

This document describes version 1.4 of the Microsoft Dynamics 365 Business Central (OData) integration. In the connection form, the version is displayed in the Source system area, for example Version: 1.4.0. Bugfix versions such as 1.4.1 are applied automatically and do not change the options described on this page. The changes of each version are listed in the release notes.

Technical Details of the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

The Microsoft Dynamics 365 Business Central (OData) integration uses the script #3724-GenericDataUploadViaODatav4 and is executed by the Lucanet.Script Execution Application (SEA). It reads the data from the OData v4 web services of Business Central and signs in with Microsoft Entra ID through the OAuth 2.0 client credentials flow. Lucanet.Financial Client is not involved.

The Microsoft Dynamics 365 Business Central (OData) integration writes the data in raw form. It does not map or transform any values into a target schema: the fields of the entity are stored as the web service returns them. The data types of the columns are taken from the OData metadata of the web service. You can join, filter, or map the data later in the Data Lake.

Prerequisites for the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

The Microsoft Dynamics 365 Business Central (OData) integration in Data Hub requires the following prerequisites. They concern the environment and are not options of the integration:

  • A license for the Microsoft Dynamics 365 Business Central (OData) integration. Without a license, Microsoft Dynamics 365 Business Central (OData) is not displayed in the Source system drop-down list.
  • A running SEA instance that executes the Microsoft Dynamics 365 Business Central (OData) integration
  • An app registration in Microsoft Entra ID with a client secret, which can sign in through the OAuth 2.0 client credentials flow. The app registration requires the application permission API.ReadWrite.All for Dynamics 365 Business Central, with admin consent. In Business Central, the app registration must be set up and enabled on the Microsoft Entra Applications page, with permission sets that grant read access to the required data. The SUPER permission set cannot be assigned to applications. For more information, see Using Service to Service Authentication in the Microsoft documentation.
  • The entities to be read, published as OData v4 web services in Business Central
  • Network access over HTTPS from the SEA instance to login.windows.net and to the host of the Business Central web services

Importing Data with the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

To import data with the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub, proceed as follows:

1

Create a connection with Microsoft Dynamics 365 Business Central (OData) as the source system and enter the settings for accessing Business Central. For more information, see Creating a Connection for the Microsoft Dynamics 365 Business Central (OData) Integration.

2

Create a source dataset that uses the connection and specify the data to extract from the source system in its Configuration area. A connection can have one or more source datasets. For more information, see Creating a Source Dataset for the Microsoft Dynamics 365 Business Central (OData) Integration.

3

Start an import of the source dataset. Before the first import, check the points of the configuration checklist for the Microsoft Dynamics 365 Business Central (OData) integration. For more information, see Starting an Import for the Microsoft Dynamics 365 Business Central (OData) Integration.

Creating a Connection for the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

A connection of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub specifies the settings that Data Hub uses to access Business Central.

To create a connection for the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub:

1

In the main menu, select Data Hub. The Integrations page is displayed as follows, for example:

Shows the 'Integrations' page in Data Hub with the 'Create new connection' button and a table with the columns 'Connection name, Number of associated data sources', 'Source system', 'Status', 'Created by', and 'Import'. The table lists connections with the source systems 'Microsoft Dynamics 365 Business Cen', truncated in the column, and 'SAP S/4HANA (RFC)', all with the status 'Active'. Highlighted in red is 'Data Hub' in the main menu.
Connections and their source datasets on the 'Integrations' page
2

In the top-right corner, click Create new connection. The connection form is displayed as follows, for example:

Shows the connection form in Data Hub with the empty 'Enter connection name' field and the message 'This field is required.', the 'Test connection', 'Cancel', and 'Create' buttons in the top-right corner, and the open 'Source system' drop-down list with the options 'Microsoft Dynamics 365 Business Central (JDBC)', 'Microsoft Dynamics 365 Business Central (OData)', 'Microsoft Dynamics 365 Business Central Beta', and 'SAP S/4HANA (RFC)'.
Connection form with the source-system selection
3

In the Source system drop-down list, select Microsoft Dynamics 365 Business Central (OData). The version of the integration is displayed in the top-right corner of the Source system area.

4

At the top of the connection form, enter a name for the connection in the Enter connection name field. The name identifies the connection on the Integrations page.

5

In the Configuration area, select the SEA instance that runs the connection. For more information, see Lucanet.Script Execution Application.

6

In the Authentication area of a Microsoft Dynamics 365 Business Central (OData) connection, enter the following information:

OptionRequiredDescriptionExample
EndpointYesURL of the OData v4 service root of the Business Central environment. The URL must not contain the company, for example Company('CRONUS'). You specify the company in the source dataset.https://api.businesscentral.dynamics.com/v2.0/<tenant-id>/Production/ODataV4/
Client IDYesApplication (client) ID of the app registration in Microsoft Entra ID00000000-0000-0000-0000-000000000000
Client SecretYesClient secret of the app registration(secret)
Tenant IDYesDirectory (tenant) ID of the Microsoft Entra ID tenant of the app registration00000000-0000-0000-0000-000000000000
ResourceNoResource that the access token is requested for. If you leave the field empty, https://api.businesscentral.dynamics.com is used.https://api.businesscentral.dynamics.com
7

Optionally, enter a description of the connection in the Description field at the bottom of the connection form.

8

Optionally, click Test connection in the top-right corner to check whether Data Hub can reach Business Central with the settings you have entered. Data Hub tests the settings without saving them. For more information, see Testing a Connection.

9

Click Create. The connection is created and displayed on the Integrations page.

Creating a Source Dataset for the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

A source dataset of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub specifies which data to import from Business Central. Each source dataset belongs to a connection, and a connection can have one or more source datasets.

You create a source dataset for the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub in three parts, in this order: first the general options of the source dataset, then the Upload configuration tab of the Configuration area, and finally saving the source dataset.

To specify the general options of a source dataset for the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub:

1

On the Integrations page, click the Three-dot icon icon in the row of the Microsoft Dynamics 365 Business Central (OData) connection and select Create new dataset.

2

In the Name field, enter a name for the source dataset. The name identifies the source dataset on the Integrations page.

3

In the Connection drop-down list, check the connection. The connection from which you create the source dataset is preselected. If necessary, you can select a different connection. The Configuration area then displays the options of the selected source system. After the source dataset is created, the connection can no longer be changed.

4

In the Namespace field, enter a technical identifier for the source dataset. The namespace is used to reference the data tables of the source dataset in SQL queries against the Data Lake, for example namespace.table_name. The namespace can have up to 255 characters and must be SQL-safe, with no spaces or unsupported special characters.

5

Optionally, define variables in the Variables area. Variables are placeholders in the configuration whose values are selected every time an import is started. For more information, see Variables.

The Variables area is displayed as follows, for example:

Shows the 'Variables' area of a source dataset in Data Hub with the columns 'Variable name', 'Display name', 'Data type', and 'Selection type' and the variables 'PERIOD' ('Period', 'String', 'Single value', 3 values) and 'YEAR' ('Fiscal year', 'String', 'Single value'), and the 'Add variable' button. Highlighted in red is 'Configure values' in the row of the variable 'YEAR'.
Variables area of a source dataset

Configuring the 'Upload configuration' Tab

In the Configuration area of a Microsoft Dynamics 365 Business Central (OData) source dataset, the Upload configuration tab contains all options of the source dataset. Each source dataset reads exactly one entity of one company. To read several entities or companies, create one source dataset for each.

The following table describes the options on the Upload configuration tab of the Microsoft Dynamics 365 Business Central (OData) integration:

OptionRequiredDescriptionExample
Current companyYesName of the Business Central company whose data is read. Required for every import, even if Use fixed navigation filter 'Company' is not selected. In that case, the company is not used to read the data.CRONUS International Ltd.
Current entityYesName of the entity to read, exactly as it is published in the OData metadata of the endpoint, for example the service name of a web service. If the entity is not found, the import fails with an error.Chart_of_Accounts
Query parametersNoOData query options that restrict or sort the data. Each query option is entered in its own row with the columns Query option and Value. For more information, see Query Parameters.Filter, Account_Type eq 'Posting'
Use fixed navigation filter 'Company'NoIf selected, the integration reads the entity of the company in Current company. Select this option for entities that belong to a company.Selected

Query Parameters

The Query parameters table on the Upload configuration tab of the Microsoft Dynamics 365 Business Central (OData) integration contains the OData query options of the request. In the Query option column, you select one of the following query options, and in the Value column, you enter its value:

Query optionValue
SelectComma-separated list of the fields to read. Every field must exist in the entity. The fields define the columns of the dataset in the Data Lake, in the order listed. If you do not use Select, all fields of the entity are read, except navigation properties.
FilterOData filter expression. The expression must contain at least one of the operators eq, ne, gt, ge, lt, le, and, or, not, in, or has.
OrderByComma-separated list of the fields to sort by, each optionally followed by asc or desc
TopMaximum number of records to read, as a whole number of 0 or more
SkipNumber of records to skip, as a whole number of 0 or more
SearchFree-text search of up to 200 characters

The following rules apply to the Query parameters table of the Microsoft Dynamics 365 Business Central (OData) integration:

  • Each query option can be used only once.
  • Every row requires a value.
  • If a rule is violated, or if a field in Select does not exist in the entity, the import fails with an error.

Data Types in the Data Lake

The Microsoft Dynamics 365 Business Central (OData) integration takes the data types of the columns from the OData metadata of the entity. The following table describes how the OData data types are stored in the Data Lake:

OData data typeData type in the Data Lake
Edm.BooleanBoolean
Edm.Byte, Edm.SByteByte
Edm.Int16, Edm.Int32, Edm.Int64Integer of the matching size
Edm.Single, Edm.DoubleFloating-point number
Edm.DecimalDecimal number with 2 decimal places. Additional decimal places, for example of exchange rates or quantities, are not stored.
Edm.DateDate
Edm.TimeOfDay, Edm.DurationTime
Edm.DateTimeOffsetDate and time
All other data types, for example Edm.String and Edm.GuidText

Example Configuration for the 'Upload configuration' Tab

The following example shows a source dataset configuration of the Microsoft Dynamics 365 Business Central (OData) integration that reads the number, name, and account type of all posting accounts of one company from the chart of accounts:

OptionValue
Current companyCRONUS International Ltd.
Current entityChart_of_Accounts
Query parametersSelect, No, Name, Account_Type
Filter, Account_Type eq 'Posting'
Use fixed navigation filter 'Company'Selected

The example is a pattern: the names of the entity and its fields depend on the web services published in the Business Central system.

Saving the Source Dataset

To save the Microsoft Dynamics 365 Business Central (OData) source dataset, click Create. The source dataset is created and displayed under the selected connection on the Integrations page.

After the first import, a source dataset can no longer be edited. Before the first import, all options except the connection can still be changed.

Starting an Import for the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

An import of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub extracts the data defined in a source dataset from Business Central and writes it into the Data Lake. The Microsoft Dynamics 365 Business Central (OData) integration checks the configuration of the source dataset when the import is executed. It reads the data page by page, with up to 10,000 records per page.

How an import of the Microsoft Dynamics 365 Business Central (OData) integration changes the data in the Data Lake depends on whether the source dataset uses variables. For more information, see Starting an Import in Data Hub.

To start an import of a Microsoft Dynamics 365 Business Central (OData) source dataset in Data Hub:

1

On the Integrations page, click the Three-dot icon icon in the row of the source dataset you want to import.

2

Select Start import. If the source dataset uses no variables, Data Hub executes the import immediately.

If the source dataset uses variables, the Start Import Execution dialog is displayed as follows, for example:

Shows the 'Start Import Execution' dialog in Data Hub for the dataset 'dataset 2025-2026' with the text 'Set the import variables, then run the extraction.', the variable 'Period' set to 'January', and the open drop-down list of the variable 'Fiscal year' with the values '2025' and '2026'.
'Start Import Execution' dialog of a source dataset with two variables
3

In the Start Import Execution dialog, select a value for every variable of the source dataset, then click Execute.

Data Hub imports the data and records the execution in the execution history of the source dataset. For more information on the execution history, see Importing Data.

Configuration Checklist for the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

After the first import, a source dataset of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub can no longer be edited. Before the first import, check the following points:

  • The connection uses Microsoft Dynamics 365 Business Central (OData) as the source system, and Endpoint, Client ID, Client Secret, and Tenant ID in the Authentication area are filled in.
  • The Endpoint contains the OData v4 service root of the Business Central environment, without the company.
  • The source dataset uses this connection.
  • On the Upload configuration tab, Current company and Current entity are filled in.
  • For an entity that belongs to a company, Use fixed navigation filter 'Company' is selected.
  • In the Query parameters table, each query option is used only once and has a value.

Release Notes for the Microsoft Dynamics 365 Business Central (OData) Integration in Data Hub

The release notes of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub list the changes of each version with new or changed options, newest first. Bugfix versions are not listed.

Version 1.4

Version 1.4 is the first documented version of the Microsoft Dynamics 365 Business Central (OData) integration in Data Hub. It is based on version 1.4 of the script #3724-GenericDataUploadViaODatav4.

This content was generated using AI and reviewed by Lucanet subject matter experts before publication.

Page IDKB9484363

Last updated on Nov 13, 2026

Table of Contents
OverviewTechnical Details of the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubPrerequisites for the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubImporting Data with the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubCreating a Connection for the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubCreating a Source Dataset for the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubConfiguring the 'Upload configuration' TabSaving the Source DatasetStarting an Import for the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubConfiguration Checklist for the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubRelease Notes for the Microsoft Dynamics 365 Business Central (OData) Integration in Data HubVersion 1.4
Related Articles

Company

Legal Notice

© Copyright 2026 - Lucanet AG