Microsoft Dynamics 365 Business Central Beta

Microsoft Dynamics 365 Business Central is an enterprise resource planning system.

Features

Setup guide

Follow our step-by-step Microsoft Dynamics 365 Business Central setup guide to connect Business Central with your destination using Fivetran connectors.

Sync overview

We use custom API pages to sync your Business Central data into your destination. The API pages expose the source tables and their fields to the API and allow us to retrieve the data stored in them.

Fivetran provides pre-defined API pages for the standard Business Central tables. If you want to add a new table to your account and sync its data using our connector, you must create an API page for the table and expose it to the API. We will use the API page to sync the data stored in the table.

NOTE: For more information about creating tables and API pages in Business Central, see Business Central's documentation.

Capture updates and new records

To capture updates and new records, we incrementally sync all the tables.

Capture deletes

By default, we use custom subscriptions to capture deletes.

If we do not have a custom subscription for a company or table, we do the following to capture deletes:

• If we do not have a custom subscription for a company, we re-import all the tables associated with the company.
• If we do not have a custom subscription for a particular table, we only re-import that table.

Sync notes

• If a table is exposed through multiple API pages, we sync all records and columns in the table into a single table in your destination. This is irrespective of the company, route, entityName, and entitySetName of the API pages.

• Shared tables which have the dataPerCompany attribute set as false in the source does not have the company_id column in the destination because the records across all companies are same.

• If a table is exposed under multiple companies, you can use the company_id column in the corresponding destination table to identify the company for its records.

• We do not sync a table if:

  • the apiPublisher property in its API page is set to microsoft
  • the apiPublisher property in its API page is set to fivetran and the apiGroup property is set to metadata or webhook

• We do not sync any data for API pages with routes used by Business Central, such as v1.0, v2.0, beta, etc.

Schema information

This schema applies to all Microsoft Dynamics 365 Business Central connectors.

Limitations

• We do not support API pages that require any kind of input to filter specific records. For example, we do not support an API page that requires the parent record's ID to retrieve the records of the child table.

  NOTE: API pages must not have triggers which needs an input to retrieve records (for example OnFindRecord).

• We do not sync a table if it has multiple API pages that return different records. Therefore, make sure all API pages for a table return the same records. If you apply any filters on an API page, make sure you apply the same filters on all the API pages defined for the table.

• We do not sync tables of Temporary type. This is because such tables are a view of other tables and the deletes are triggered on the original table instead of the temporary table.

• All destination tables have the systemId column as the primary key even though the source table has a different primary key.

• If a table has multiple API pages, we make separate API requests for each page. The records in the table may be updated between these API requests. In such a scenario, the records in your destination may not contain the latest values for some columns. However, we resolve this data discrepancy in the subsequent syncs.

• We ignore the API pages that filter records based on the sourceTableView property.

• We ignore the API pages that do not have the systemId and systemModifiedAt columns.