Connecting Business Central

This guide explains how to connect Demiton to Microsoft Dynamics 365 Business Central.

The integration allows workflows to retrieve and write financial data such as:

• vendors
• projects
• purchase orders
• project ledger entries

Once connected, Blueprints can safely execute workflows that interact with the ERP.

Prerequisites

Before creating the connection, ensure the following:

• 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 the following values:

Tenant ID
Client ID
Client Secret
Business Central environment URL

Step 1: Register an Entra ID Application

Navigate to the Azure Portal and register a new application.

The application represents Demiton when interacting with Business Central.

During registration:

• select single tenant access
• generate a client secret

Record the following values:

Tenant ID
Application (Client) ID
Client Secret

These credentials will be used by the adapter.

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.

Step 3: Configure the Adapter

Create a Business Central connection inside the Demiton platform.

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

The adapter factory uses these credentials to create a Business Central adapter.

Step 4: Discover Available Resources

Once the connection is created, the adapter performs resource discovery.

Typical resources exposed include:

• vendors
• projects
• project_ledger_entries
• purchase_orders

These resources become available to Blueprint workflows.

Step 5: Test Data Retrieval

Create a simple workflow step to confirm the integration.

Example:

FETCH → business_central.projects

If the configuration is correct, the adapter returns project records.

These records are wrapped inside a standardized response envelope.

Security Considerations

Business Central connections should follow several security practices:

• store credentials securely
• restrict application permissions to required entities
• rotate client secrets periodically
• use sandbox environments during testing

These practices reduce operational risk and ensure secure system interaction.

Next Steps

Once Business Central is connected, you can build workflows such as:

• project synchronization
• labour cost posting
• vendor reconciliation
• financial reporting pipelines

These workflows ensure that ERP data remains aligned with operational systems.

---