Skip to content
ERP ⇄ Analytics

Microsoft Dynamics GP to Tableau integration — real-time data sync

Keep Microsoft Dynamics GP 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 Microsoft Dynamics GP and Tableau

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

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Microsoft Dynamics GP, so Microsoft Dynamics GP 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 Microsoft Dynamics GP 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 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 02 Read Databases, Tables, and Fields from the Metadata API to populate a data catalog with Tableau lineage and column definitions.
  • 03 Replicate GP company databases into a warehouse for financial and operational reporting.
  • 04 Sync customers and invoices between GP and a CRM so sales sees balances and billing history.

Common sync patterns

Where Microsoft Dynamics GP is the HR system of record: workforce and cost analysis

Worker and organization data from Microsoft Dynamics GP syncs into Tableau for headcount, cost, and utilization reporting alongside other company data.

Write-back where Microsoft Dynamics GP exposes writable fields: segments and scores return

Segments, scores, or metrics computed in Tableau sync onto the matching records in Microsoft Dynamics GP, so operations act on what the analysis found.

Where Microsoft Dynamics GP holds the books: revenue and finance dashboards from live data

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

What you can sync between Microsoft Dynamics GP 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.

Microsoft Dynamics GP objects Tableau objects How this pairing syncs
Vendors Payables master records aligned with procurement and AP automation. 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. Vendors is specific to Microsoft Dynamics GP and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Sales Documents (SOP) is specific to Microsoft Dynamics GP and Workbooks to Tableau — each maps to any object or custom field on the other side.
Purchase Orders (POP) Procurement documents reconciled with receiving and vendor systems. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Purchase Orders (POP) is specific to Microsoft Dynamics GP and Views to Tableau — each maps to any object or custom field on the other side.
Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Inventory Items (IV) is specific to Microsoft Dynamics GP and Projects to Tableau — each maps to any object or custom field on the other side.
GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. 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. GL Accounts & Journal Entries is specific to Microsoft Dynamics GP and Users to Tableau — each maps to any object or custom field on the other side.
Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Databases and Tables to Tableau — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics GP 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.

Microsoft Dynamics GP Tableau Sub-second propagation

DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.

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 Microsoft Dynamics GP records.

Tableau Microsoft Dynamics GP 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 applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.

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 Microsoft Dynamics GP ⇄ Tableau

Connect Microsoft Dynamics GP and Tableau for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics GP–Tableau connection.

Real-time

Real-time sync

Changes in Microsoft Dynamics GP or Tableau instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics GP 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 Microsoft Dynamics GP or Tableau record.

Observability

Monitoring

Track your Microsoft Dynamics GP ⇄ Tableau sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP and Tableau.

How the Microsoft Dynamics GP and Tableau connectors work

Microsoft Dynamics GP

Integration surface
SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
Authentication
SQL Server credentials or Windows authentication
Change detection
SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
Capabilities
read · write · CDC

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 Microsoft Dynamics GP 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 Microsoft Dynamics GP 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
    Microsoft Dynamics GP connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics GP 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 · Microsoft Dynamics GP ⇄ 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
    Microsoft Dynamics GP Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Dynamics GP 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 437 integrations available for Microsoft Dynamics GP and Tableau.

Popular · 8 of 437
All Microsoft Dynamics GP 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