Two-way sync
Changes in Egnyte or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep Egnyte 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.
Dynamics 365 Business Central runs the business on structured records: Journals, Dimensions, Payments, Customers. Egnyte holds files and the metadata that describes them: Users, Groups, Permissions, Links. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Dynamics 365 Business Central touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Egnyte, from signed contracts to vendor bills to receipts, describe a transaction Dynamics 365 Business Central needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Journals, Dimensions, Payments, Customers in Dynamics 365 Business Central and Users, Groups, Permissions, Links in Egnyte in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Egnyte already labeled and filed, and metadata captured against a stored file can create or update the matching record in Dynamics 365 Business Central. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Dynamics 365 Business Central and the file in Egnyte never describe two different versions of the same document.
Every transaction's supporting file lives in Egnyte beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Dynamics 365 Business Central.
Files that Dynamics 365 Business Central produces land in Egnyte labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
Record fields from Dynamics 365 Business Central, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Egnyte, so storage stays organized without anyone tagging by hand.
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.
| Egnyte objects | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. | Items Product and inventory records aligned with e-commerce and warehouse systems. | Permissions is specific to Egnyte and Items to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Links Shared file and folder links created, listed, and revoked via the Links API; useful for governing and auditing external sharing. | Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | Links is specific to Egnyte and Sales Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Metadata Custom metadata keys and project fields on files/folders via the Metadata API; written for classification and read back for reporting. | Sales Invoices Billing documents synced to CRMs and payment platforms. | Metadata is specific to Egnyte and Sales Invoices to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Events and Audit reports File, login, permission, and sharing activity read via the Events API and Audit Reporting API; consumed read-only for compliance. | Purchase Orders Procurement documents exchanged with supplier-facing systems. | Events and Audit reports is specific to Egnyte and Purchase Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Files File content managed via the fs-content endpoint (upload/download, chunked for large files); synced two-way with other stores. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Files is specific to Egnyte and General Ledger Entries to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Folders Folder hierarchy managed via the fs endpoint (create, move, rename, delete); the tree structure is mirrored during sync. | Journals Staging records for financial postings created by integrations before posting. | Folders is specific to Egnyte and Journals 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.
DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.
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 written to Egnyte through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Egnyte–Dynamics 365 Business Central connection.
Changes in Egnyte or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Egnyte 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 Egnyte or Dynamics 365 Business Central record.
Track your Egnyte ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Egnyte 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 Egnyte 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 Egnyte 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 Egnyte and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Egnyte's Permissions and Links), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Egnyte and Dynamics 365 Business Central. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Egnyte: Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata, permission, and comment events. On Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Dynamics 365 Business Central side: Journals, Dimensions, Payments, Customers, plus custom fields where Dynamics 365 Business Central exposes them. On the Egnyte side: Users, Groups, Permissions, Links. Stacksync auto-detects both schemas and converts types between the two systems.
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 Egnyte and Dynamics 365 Business Central: Audit-ready retention; Documents filed with their context; Metadata that files itself. Every transaction's supporting file lives in Egnyte beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Dynamics 365 Business Central.
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 500 integrations available for Egnyte and Dynamics 365 Business Central.