Two-way sync
Changes in Dynamics 365 Business Central or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamics 365 Business Central and Onelogin in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
An ERP and an identity system describe the same workforce from two angles. Dynamics 365 Business Central holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Onelogin controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Dynamics 365 Business Central and their account still being active in Onelogin is a real security exposure.
Stacksync syncs General Ledger Entries, Journals, Dimensions, Payments in Dynamics 365 Business Central with Users, Roles, Apps (app instances), Groups in Onelogin in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.
A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
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 | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Items Product and inventory records aligned with e-commerce and warehouse systems. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Items is specific to Dynamics 365 Business Central and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Sales Orders is specific to Dynamics 365 Business Central and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| Sales Invoices Billing documents synced to CRMs and payment platforms. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Sales Invoices is specific to Dynamics 365 Business Central and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. | Purchase Orders is specific to Dynamics 365 Business Central and Groups to Onelogin — 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. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | General Ledger Entries is specific to Dynamics 365 Business Central and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. | |
| Journals Staging records for financial postings created by integrations before posting. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Journals is specific to Dynamics 365 Business Central and Events to Onelogin — 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.
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 written to Onelogin through its API, with automatic retries and rate-limit backoff.
DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Onelogin connection.
Changes in Dynamics 365 Business Central or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central or Onelogin data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamics 365 Business Central or Onelogin record.
Track your Dynamics 365 Business Central ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Onelogin.
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 Dynamics 365 Business Central and Onelogin 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 Dynamics 365 Business Central and Onelogin 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 Dynamics 365 Business Central and Onelogin: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Items and Sales Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
Dynamics 365 Business Central: The standard API exposes entities as OData v4 endpoints and supports $filter on lastModifiedDateTime, giving integrations a built-in incremental cursor. Onelogin: The Event Webhook (Event Broadcaster) delivers batches of events to a registered URL for near-real-time triggers, while the Events API filters by since/until for historical pulls; there is no database-level CDC. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central and Onelogin 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 Dynamics 365 Business Central and Onelogin records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamics 365 Business Central and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 Business Central–Onelogin integration in-house.
Yes — Stacksync ships production-grade connectors for both Dynamics 365 Business Central and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. On Onelogin: Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 507 integrations available for Dynamics 365 Business Central and Onelogin.