Skip to content
ERP ⇄ Analytics

Dynamics 365 Business Central to Tableau integration — real-time data sync

Keep Dynamics 365 Business Central and Tableau in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dynamics 365 Business Central and Tableau

Put Dynamics 365 Business Central's records into Tableau as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Tableau computes back where Dynamics 365 Business Central can use them.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Dynamics 365 Business Central, so Dynamics 365 Business Central always reflects the current state of Tableau — without exports, scripts, or schedulers.

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Dynamics 365 Business Central carries financials, operations, workforce data, or all three, those numbers belong in Tableau, next to the product, behavioral, and web data the team already measures.

Common use cases

  • 01 Track Extract Refresh Tasks and DatasourceRefreshFailed webhook events to raise alerts in a database or ticketing system when refreshes fail.
  • 02 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 03 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
  • 04 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.

Common sync patterns

Where Dynamics 365 Business Central holds the books: revenue and finance dashboards from live data

Financial records from Dynamics 365 Business Central land in Tableau as they change, so revenue, margin, and spend dashboards read current figures rather than last night's export.

Where Dynamics 365 Business Central runs order-to-cash: customer and account analytics

Orders, invoices, and account records from Dynamics 365 Business Central join the behavioral and usage data Tableau already tracks, so customer analysis spans activity and dollars in one view.

Where Dynamics 365 Business Central runs operations: inventory and fulfillment metrics

Operational records from Dynamics 365 Business Central become measurable in Tableau, joinable with the rest of what the company tracks for supply and fulfillment reporting.

What you can sync between Dynamics 365 Business Central and Tableau

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Dynamics 365 Business Central objects Tableau objects How this pairing syncs
Purchase Orders Procurement documents exchanged with supplier-facing systems. Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Purchase Orders is specific to Dynamics 365 Business Central and Fields and Columns to Tableau — each maps to any object or custom field on the other side.
General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. Published Data Sources Published data sources (.tdsx); their underlying rows are read via the VizQL Data Service, and refresh state is tracked through content webhooks. General Ledger Entries is specific to Dynamics 365 Business Central and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Journals Staging records for financial postings created by integrations before posting. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Journals is specific to Dynamics 365 Business Central and Workbooks to Tableau — each maps to any object or custom field on the other side.
Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Dimensions is specific to Dynamics 365 Business Central and Views to Tableau — each maps to any object or custom field on the other side.
Payments Customer and vendor payment records reconciled against invoices. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Payments is specific to Dynamics 365 Business Central and Projects to Tableau — each maps to any object or custom field on the other side.
Customers Core master data synced with CRMs so sales and finance share one customer list. Users Site users with site roles and group membership; read via REST for access reviews and to reconcile identities against an HR or IdP source. Customers is specific to Dynamics 365 Business Central and Users to Tableau — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central and Tableau

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Dynamics 365 Business Central Tableau Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating Dynamics 365 Business Central records.

Tableau Dynamics 365 Business Central Sub-second propagation

DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
What ships with Dynamics 365 Business Central ⇄ Tableau

Connect Dynamics 365 Business Central and Tableau for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Tableau connection.

Real-time

Real-time sync

Changes in Dynamics 365 Business Central or Tableau instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 Business Central or Tableau data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dynamics 365 Business Central or Tableau record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ Tableau sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Tableau.

How the Dynamics 365 Business Central and Tableau connectors work

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

Tableau

Integration surface
REST API, Metadata API (GraphQL), and VizQL Data Service
Authentication
Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
How it works

How to connect Dynamics 365 Business Central to Tableau — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Dynamics 365 Business Central and Tableau with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dynamics 365 Business Central connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 Business Central and Tableau objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dynamics 365 Business Central ⇄ Tableau
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dynamics 365 Business Central Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 Business Central and Tableau integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 441 integrations available for Dynamics 365 Business Central and Tableau.

Popular · 6 of 441
All Dynamics 365 Business Central integrations All Tableau integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own