BigQuery
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Data warehouse / ERP · Two-way sync platform
BigQuery and Dynamics 365 F&O integration — two-way sync
Keep supported BigQuery and Dynamics 365 F&O records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
- Field mappings and sync direction under your control
- Inspect and resolve record errors in one dashboard
Built for teams where self-serve, reliability and scale matter
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
Example workflow
Customer reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving the proposed customer table in BigQuery or Dynamics 365 F&O Customers needs a defined result in the other system.
Start with the proposed customer table in BigQuery and Dynamics 365 F&O Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Review records and field ownershipMapping essentials
Records and field ownership
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| BigQuery record | Dynamics 365 F&O record | Record matching | Field ownership |
|---|---|---|---|
| Proposed customer tableProposed table; choose its name and schema.Reporting dataset | CustomersProposed record; confirm Stacksync object support. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| Proposed customer invoice tableProposed table; choose its name and schema.Reporting dataset | Customer InvoicesProposed record; confirm Stacksync object support. | Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. | The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite. |
| Proposed supplier bill tableProposed table; choose its name and schema.Reporting dataset | Vendor InvoicesProposed record; confirm Stacksync object support. | Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. | Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect BigQuery and Dynamics 365 F&O
Put your BigQuery and Dynamics 365 F&O data to work
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one BigQuery and Dynamics 365 F&O workflow to test, define what success looks like, and decide who handles failed updates.
Analyze Customer and Sales Order history at scale in BigQuery without loading the Dynamics 365 F&O instance.
Track vendor spend by joining Purchase Orders to Vendor records within one BigQuery Project.
Feed demand forecasting models from Released Products and Sales Orders kept current in BigQuery Tables.
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Dynamics 365 F&O
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Requires account access and compatible change tracking. Confirm field permissions and sync direction. |
| Requires API exposure and compatible change tracking. Confirm field permissions and sync direction. |
Connection essentials
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | BigQuery | Dynamics 365 F&O |
|---|---|---|
| Integration interface | GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs | OData REST endpoint over data entities, plus the Data Management Framework for batch |
| Authentication | Dedicated Google Cloud service account and JSON key | OAuth via Microsoft sign-in |
| Change detection | The setup provisions notification services using Eventarc and Cloud Run in the customer Google Cloud project. | Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
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.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
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:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
BigQuery
- Integration interface
- GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
- Authentication
- Dedicated Google Cloud service account and JSON key; enable the APIs and grant the roles in the authorization guide.
- Change detection
- The setup provisions notification services using Eventarc and Cloud Run in the customer Google Cloud project.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Enable BigQuery, Cloud Run, Cloud Resource Manager, and Eventarc APIs in the target project.
- Create a dedicated service account with the roles in the authorization guide and supply its credentials through Stacksync.
Limitations to check
- Only tables are supported in the saved guide; ordinary and materialized views are excluded.
- Google Cloud quotas and the selected write method affect capacity; validate the current project limits before a large backfill.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Dynamics 365 F&O
- Integration interface
- OData REST endpoint over data entities, plus the Data Management Framework for batch
- Authentication
- OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
- Change detection
- Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required.
- Enable change tracking for each selected entity and check whether changes in child tables are included.
Limitations to check
- Some complex entities cannot enable change tracking. Primary-table tracking does not capture changes in child tables.
Technical documentation
- Authorize Dynamics 365 F\&O
- Dynamics 365 Finance and Operations
- Enable Changes Detection Capture (CDC)
- Make a Custom Entity Syncable by Stacksync
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare BigQuery and Dynamics 365 F&O access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
BigQuery setup checklist
- Enable BigQuery, Cloud Run, Cloud Resource Manager, and Eventarc APIs in the target project.
- Create a dedicated service account with the roles in the authorization guide and supply its credentials through Stacksync.
Setup guides: Authorize BigQuery
Dynamics 365 F&O setup checklist
- Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required.
- Enable change tracking for each selected entity and check whether changes in child tables are included.
Setup guides: Authorize Dynamics 365 F\&O
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the BigQuery and Dynamics 365 F&O planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Proposed customer table in BigQuery (choose its name) / Customers
Plan a customer dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- BigQuery
- Your database schema
- Dynamics 365 F&O
- Object support to establish
- Record identity
- Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
- Field ownership
- Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
- Source customer ID
- Person/company classification
- Legal entity or business unit
- Destination identity reference
- Record dependencies
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Validation
- Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
- Recovery
- Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
References: Dynamics 365 F&O: Customers documentation
Reporting dataset
Proposed customer invoice table in BigQuery (choose its name) / Customer Invoices
Plan a customer invoice dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- BigQuery
- Your database schema
- Dynamics 365 F&O
- Object support to establish
- Record identity
- Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
- Field ownership
- The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Fields to include
- Source invoice ID
- Customer or supplier reference
- Line totals
- Currency
- Posting/payment status
- Record dependencies
- Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
- Validation
- Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
- Recovery
- Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
References: Dynamics 365 F&O: Customer Invoices documentation
Reporting dataset
Proposed supplier bill table in BigQuery (choose its name) / Vendor Invoices
Plan a supplier bill dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- BigQuery
- Your database schema
- Dynamics 365 F&O
- Object support to establish
- Record identity
- Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
- Field ownership
- Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.
Fields to include
- Source bill ID
- Supplier reference
- Entity
- Line amounts and currency
- Approval/posting state
- Record dependencies
- Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
- Validation
- Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
- Recovery
- Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
References: Dynamics 365 F&O: Vendor Invoices documentation
Reporting dataset
Proposed sales order table in BigQuery (choose its name) / Sales Orders
Plan a sales order dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- BigQuery
- Your database schema
- Dynamics 365 F&O
- Object support to establish
- Record identity
- Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
- Field ownership
- Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Fields to include
- Source order ID
- Customer reference
- Line references and quantities
- Order status
- Currency
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
References: Dynamics 365 F&O: Sales Orders documentation
Reporting dataset
Proposed supplier or vendor table in BigQuery (choose its name) / Vendors
Plan a supplier or vendor dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- BigQuery
- Your database schema
- Dynamics 365 F&O
- Object support to establish
- Record identity
- Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
- Field ownership
- Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.
Fields to include
- Source supplier ID
- Legal name
- Entity reference
- Payment terms
- Active status
- Record dependencies
- Resolve business-unit and payment-term references before purchasing transactions.
- Validation
- Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
- Recovery
- Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
References: Dynamics 365 F&O: Vendors documentation
Reporting dataset
Proposed journal or ledger entry table in BigQuery (choose its name) / General Journal Entries
Plan a journal or ledger entry dataset while preserving its source meaning.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- BigQuery
- Your database schema
- Dynamics 365 F&O
- Object support to establish
- Record identity
- Retain journal ID and line IDs within the legal entity and accounting period.
- Field ownership
- The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row.
Fields to include
- Source journal ID
- Account references
- Debit/credit amounts
- Entity
- Accounting period
- Record dependencies
- Resolve chart-of-account, currency, entity, and dimension references before lines.
- Validation
- Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
- Recovery
- Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
References: Dynamics 365 F&O: General Journal Entries documentation
Compare integration approaches
Use BigQuery Proposed customer table in BigQuery (choose its name) and Dynamics 365 F&O Customers for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Stacksync managed sync
- Best fit
- Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your BigQuery and Dynamics 365 F&O record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Proposed customer table in BigQuery (choose its name) / Customers, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when BigQuery and Dynamics 365 F&O need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time BigQuery / Dynamics 365 F&O migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Customer reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Proposed customer table in BigQuery (choose its name) or Customers record needs a defined result in the other system.
- Start with BigQuery Proposed customer table in BigQuery (choose its name) and Dynamics 365 F&O Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Customer invoice reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Proposed customer invoice table in BigQuery (choose its name) or Customer Invoices record needs a defined result in the other system.
- Start with BigQuery Proposed customer invoice table in BigQuery (choose its name) and Dynamics 365 F&O Customer Invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Supplier bill reporting workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Proposed supplier bill table in BigQuery (choose its name) or Vendor Invoices record needs a defined result in the other system.
- Start with BigQuery Proposed supplier bill table in BigQuery (choose its name) and Dynamics 365 F&O Vendor Invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Reconcile Dynamics 365 F&O business records with BigQuery
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A finance-owned record in Dynamics 365 F&O needs operational visibility through a selected destination dataset.
- Select Customers or Vendors with the correct legal entity, period, and currency.
- Define a reporting relationship in BigQuery; do not equate customer records, ledger accounts, and posted transactions.
- Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Proposed customer table in BigQuery (choose its name) / Customers
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Proposed customer invoice table in BigQuery (choose its name) / Customer Invoices
Test case
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Expected result
The expected customer invoice relationship is preserved with no duplicate action or unintended write.
Proposed supplier bill table in BigQuery (choose its name) / Vendor Invoices
Test case
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Expected result
The expected supplier bill relationship is preserved with no duplicate action or unintended write.
Proposed sales order table in BigQuery (choose its name) / Sales Orders
Test case
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated customer change
Investigate
Inspect BigQuery Proposed customer table in BigQuery (choose its name) and Dynamics 365 F&O Customers, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Rejected or repeated customer invoice change
Investigate
Inspect BigQuery Proposed customer invoice table in BigQuery (choose its name) and Dynamics 365 F&O Customer Invoices, their IDs, and the destination error.
Next action
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Rejected or repeated supplier bill change
Investigate
Inspect BigQuery Proposed supplier bill table in BigQuery (choose its name) and Dynamics 365 F&O Vendor Invoices, their IDs, and the destination error.
Next action
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
A record type or update is unavailable
Investigate
Check the BigQuery and Dynamics 365 F&O connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between BigQuery and Dynamics 365 F&O
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
BigQuery Dynamics 365 F&O Timing depends on the connected systems
Detect changesThe setup provisions notification services using Eventarc and Cloud Run in the customer Google Cloud project.
Apply updatesSelected writable fields update in Dynamics 365 F&O. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Dynamics 365 F&O BigQuery Timing depends on the connected systems
Detect changesFull and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.
Apply updatesSelected writable fields update in BigQuery. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Google Cloud quotas and the selected write method affect capacity; validate the current project limits before a large backfill.
- Some complex entities cannot enable change tracking. Primary-table tracking does not capture changes in child tables.
FAQ
BigQuery and Dynamics 365 F&O integration FAQ
-
Stacksync connects BigQuery and Dynamics 365 F&O with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
-
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Enable BigQuery, Cloud Run, Cloud Resource Manager, and Eventarc APIs in the target project. Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Proposed customer table in BigQuery (choose its name) in BigQuery and Customers in Dynamics 365 F&O. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Use BigQuery Proposed customer table in BigQuery (choose its name) and Dynamics 365 F&O Customers for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 450 integrations listed for BigQuery and Dynamics 365 F&O.
Popular · 7 of 450
-
BigQuery and Oracle Fusion ERP -
BigQuery and Acumatica -
BigQuery and SAP S/4HANA -
BigQuery and Odoo -
Dynamics 365 F&O and Databricks -
Dynamics 365 F&O and Amazon S3 -
Dynamics 365 F&O and Amazon Redshift
No integrations match .
Next step
See your workflow in Stacksync
Walk through your BigQuery and Dynamics 365 F&O records, field mappings, and requirements with an integration engineer.
