Skip to content
Demiton

Connecting Business Central

This guide explains how to connect Demiton to Microsoft Dynamics 365 Business Central so that workflows can retrieve and write financial data such as vendors, projects, purchase orders, and project ledger entries.

Prerequisites

Before creating the connection, ensure:

  • Business Central environment is accessible
  • An Azure Entra ID application has been created
  • Appropriate permissions are granted to the service principal
  • The OData API endpoint is enabled

You will need:

  • Tenant ID
  • Client ID
  • Client Secret
  • Business Central environment URL

Step 1: Register an Entra ID application

In the Azure Portal, register a new application. This application represents Demiton when interacting with Business Central.

During registration:

  • Select single tenant access
  • Generate a client secret

Record the Tenant ID, Application (Client) ID, and Client Secret.

Step 2: Grant Business Central permissions

Inside Business Central, assign the application access to the required entities. Typical permissions include:

  • Vendors
  • Projects
  • Project Ledger Entries
  • Purchase Invoices

For production environments, create a dedicated permission set rather than granting broad access.

Step 3: Configure the connector

Create a Business Central connector in the platform under Connectors → Systems → New.

Example configuration:

system_type: D365_BUSINESS_CENTRAL
environment: PRODUCTION
tenant_id: <tenant_id>
client_id: <client_id>
client_secret: <client_secret>
base_url: https://api.businesscentral.dynamics.com

Step 4: Discover available resources

Once the connector is saved, the adapter performs resource discovery. Typical resources exposed include:

  • vendors
  • projects
  • project_ledger_entries
  • purchase_orders

These resources become available to workflows as fetch/push targets.

Step 5: Test data retrieval

Create a simple workflow step to confirm the integration:

FETCH → business_central.projects

Run the workflow in simulation mode (dry_run: true) first. If the configuration is correct, the adapter returns project records wrapped in a Sovereign Envelope.

Security considerations

  • Store credentials in the platform’s secure credential store — never in workflow definitions
  • Restrict application permissions to required entities only
  • Rotate client secrets on a regular schedule
  • Use sandbox environments during initial testing

Next steps