Skip to content
  • There are no suggestions because the search field is empty.

Microsoft Dynamics 365 Business Central using Power Automate

This article describes how to integrate AlisQI and MS Dynamics 365 Business Central using Power Automate.

Overview

The integration supports seamless bi-directional data synchronization between AlisQI and Microsoft Dynamics 365 Business Central (BC365), covering both master and transactional data. Common use cases include aligning item and customer information, transferring scheduled Production Orders from BC365 to AlisQI, and updating batch release statuses from AlisQI back to BC365.

Integration type
✅ Native connector (Power Automate)
✅ No-code automation
✅ Real-time event-based or scheduled triggers

 

In this article

Key Capabilities

  • Automatically create or update BC365 records (e.g., Production Orders) when data in AlisQI changes.

  • Push inspection results, certificates of analysis, or non-conformance data directly to ERP.

  • Fetch master data (e.g., item codes, suppliers) from BC365 into AlisQI.

  • Use Power Automate to orchestrate synchronization workflows.

  • Works with both cloud and on-premise BC365 environments (via the Business Central connector on Power Automate).

Architecture

Power Automate manages the entire integration flow by receiving the trigger, extracting data from the source, transforming it as needed, and injecting the processed data into the target system. 

Trigger types

  • AlisQI → BC365: triggered by a manual workflow trigger or a change in AlisQI (e.g., new inspection result, status update). This is realized with a workflow that calls a webhook.

  • BC365 → AlisQI: triggered by an event orrecord change in BC365 (via standard Business Central connector).

Technologies involved

Setup Instructions

Prerequisites

  • Active AlisQI subscription

  • Microsoft Power Automate license

  • Access to Dynamics 365 Business Central environment

  • AlisQI API admin access enabled (to manage API tokens and permissions)

Configuration Steps

Create the Power Automate flow

  1. Log in to Power Automate.

  2. Create a new Automated Flow.

  3. Search for and select the AlisQI Connector.

  4. Choose your actions, e.g. “get results from AlisQI analysis set”

  5. Add an action step using the Business Central connector, e.g. “Update a Production Order.”

  6. Map AlisQI fields to the BC365 fields.

  7. Save and test your flow.

Authenticate both connectors

  • AlisQI connector: Log in with your AlisQI tenant name and API key (generated in Integration Hub).

  • Business Central connector: Use your Microsoft credentials or a service account with API permissions.

Authentication

Method

  • AlisQI: API Key-based (entered once during connector setup). 

  • Business Central: OAuth2 via Microsoft Identity Platform.

Token management

Power Automate handles token refresh automatically; no manual maintenance required.

Read all about AlisQI API token management here.

Tip: Create an OAuth Authentication profile in AlisQI's Integration Hub to connect to Power Automate using OAuth.

Data Mapping

In connecting AlisQI to Business Central, data models need to be aligned. The actual data mapping depends on your AlisQI and BC365 data model.

Read about data modelling in AlisQI here.

Error Handling & Logging

  • Error visibility
    Power Automate logs all failed runs under My Flows → Run History.
    AlisQI logs all API and webhooks calls in the Integration hub.

  • Retries
    AlisQI does not automatically retry failed webhooks.

  • Common errors

    Error Cause Solution
    401 Unauthorized Invalid or expired API key Regenerate key in AlisQI
    404 Not Found Wrong record ID in mapping Verify flow variables
    429 Too Many Requests Exceeded rate limit Implement delay or batching

Security & Rate Limits

  • All communication uses HTTPS/TLS 1.2+.

  • API keys stored securely within Power Automate.

  • AlisQI API rate limit: 30 requests per minute per key.

  • Data processed transiently by Microsoft Power Automate; no long-term storage of payloads.

Example Flow

Scenario: Automatically update the production order in BC365 when an inspection result is recorded in AlisQI.

  1. Create a workflow in AlisQI that triggers when: Batch status is Released

  2. Let the workflow call a Power Automate webhook (http endpoint)

  3. Action 1: Retrieve item details from Business Central.

  4. Action 2: Update the related Production Order’s Quality Status field.

  5. Action 3 (optional): Send Teams notification to Quality Manager.

Troubleshooting

Problem Possible Cause Resolution
Flow not triggering Wrong event selected in trigger Check trigger type in Power Automate
BC365 action fails Missing permissions Verify service account access
Data mismatch Field type mismatch Adjust mapping or use expression conversion