For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview & Data Flow

The connector operates directly within Microsoft Dynamics 365 Business Central. From here, users start synchronizations, control mappings, and track results. The app communicates with the shop via the Magento REST API.

Work Areas at a Glance

🧭 Setup Wizard

Guides new shops through connection, initial data, and required mappings.

🧩 Mapping Hub

Shows open mappings and leads to focused detail pages.

⬇️ Download Cockpit

Bundles reference, catalog, and sales downloads with preflight checks.

🛒 Sales Order Dashboard

Links Magento orders with the corresponding BC documents.

🔎 Logs

Separate business events, API details, and product download progress.

Consciously Define Data Ownership

Magento → Business Central

  • Payment and shipping methods

  • Websites and Store Views

  • Tax references and attributes

  • Categories and products

  • Orders and optional credit memos

Business Central → Magento

  • Items and product structures

  • Categories and assignments

  • Images and related items

  • Inventory per MSI source

  • Shipment, tracking, and invoice

Not every data area is bidirectional. Define a leading system for each area. For example, the Upload Data page sends data from BC to Magento, even though some legacy labels read “Import.”

1

Verify connection and initial data

Test access and download all required reference data from Magento.

2

Complete required mappings

Review payment, shipping, tax, websites, languages, and MSI sources.

3

Test with individual transactions

Run one item, one inventory update, and one order through the full cycle.

4

Verify the result in the target system

Status fields alone are not sufficient: compare the BC record, log, and Magento result.

5

Only then automate

Activate batch sizes and Job Queue Entries step by step.