Two-way sync
Changes in Google Cloud Spanner or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and Dynamics 365 Business Central in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Sales Orders, Sales Invoices, Purchase Orders, General Ledger Entries from Dynamics 365 Business Central into Google Cloud Spanner and keeps both sides consistent in real time. Whatever Dynamics 365 Business Central is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Google Cloud Spanner sync back into Dynamics 365 Business Central with its validations respected.
Scripts and services read and write the synced tables; Stacksync handles the Dynamics 365 Business Central interface, limits, and retries.
Updates in Dynamics 365 Business Central arrive as row changes in Google Cloud Spanner, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in Google Cloud Spanner for provisioning, access, and reporting systems that read from the database.
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.
| Google Cloud Spanner objects | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Rows The unit of read and write in each sync cycle, keyed by primary key. | Sales Invoices Billing documents synced to CRMs and payment platforms. | Rows is specific to Google Cloud Spanner and Sales Invoices to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Purchase Orders Procurement documents exchanged with supplier-facing systems. | Interleaved tables is specific to Google Cloud Spanner and Purchase Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Secondary indexes is specific to Google Cloud Spanner and General Ledger Entries to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Journals Staging records for financial postings created by integrations before posting. | Change streams is specific to Google Cloud Spanner and Journals to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Views is specific to Google Cloud Spanner and Dimensions to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Databases Top-level containers that scope schema and sync configuration. | Payments Customer and vendor payment records reconciled against invoices. | Databases is specific to Google Cloud Spanner and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side. |
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.
DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Dynamics 365 Business Central connection.
Changes in Google Cloud Spanner or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or Dynamics 365 Business Central data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or Dynamics 365 Business Central record.
Track your Google Cloud Spanner ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Dynamics 365 Business Central.
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.
Authenticate Google Cloud Spanner and Dynamics 365 Business Central with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Google Cloud Spanner and Dynamics 365 Business Central 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Spanner and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Rows and Interleaved tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Google Cloud Spanner and Dynamics 365 Business Central: Internal tools and automations without API code; React to ERP changes; Where Dynamics 365 Business Central is the HR system of record: people data for internal systems. Scripts and services read and write the synced tables; Stacksync handles the Dynamics 365 Business Central interface, limits, and retries.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Dynamics 365 Business Central: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Google Cloud Spanner: Spanner provides external consistency across regions using Google's TrueTime clock infrastructure. Dynamics 365 Business Central: Custom API pages written in AL extend the same OData surface, letting partner-specific tables participate in syncs like standard entities. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and Dynamics 365 Business Central without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Google Cloud Spanner and Dynamics 365 Business Central records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 430 integrations available for Google Cloud Spanner and Dynamics 365 Business Central.