-
Role-specific: Designed for your role and journey
-
Stay informed with monthly release videos
-
Instant assistance with our AI help-bot, Zappy
-
-
In-app, context-specific doc navigation
-
Also available at docs.zapbi.com
-
Hover over elements for tooltips and quick links
-
In-app scheduled weekly ask-me-anything's (AMAs)
-
Mentoring available on-request
-
-
Filter by difficultly, topic or status (unwatched and more)
-
Use picture-in-picture mode for seamless side-by-side guidance
-
Navigate quickly with jump-to-chapter functionality
-
In-app video and AI guidance
-
Role-specific: Designed for your role and journey
-
Stay informed with monthly release videos
-
Instant assistance with our AI help-bot, Zappy
Question
Answer
How does Zap extract data from D365?
A signed deployable X++ package that runs as a batch job, pulling only delta records since last extraction using timestamp-based incremental processing.
A signed deployable X++ package that runs as a batch job, pulling only delta records since last extraction using timestamp-based incremental processing.
How does Zap extract data from D365?
Why not use OData, BYOD, or Synapse / Fabric?
OData is near-real-time but too slow for warehouse loads. Lake/Synapse/Fabric exports land every 5-15 min (typical) and can stretch to ~60 min on very large tables. Too slow for finance teams at month end.
OData is near-real-time but too slow for warehouse loads. Lake/Synapse/Fabric exports land every 5-15 min (typical) and can stretch to ~60 min on very large tables. Too slow for finance teams at month end.
Why not use OData, BYOD, or Synapse / Fabric?
Is the X++ extractor a workaround?
No. It's the same Lifecycle Services deployable-package model every certified Dynamics ISV uses (tax, EDI, etc.).
No. It's the same Lifecycle Services deployable-package model every certified Dynamics ISV uses (tax, EDI, etc.).
Is the X++ extractor a workaround?
Why hasn't Microsoft built the same real-time feed?
Microsoft provides solutions that fit within their broader ecosystem of tools and product strategy. These tools are strong for the general use case, but not strong for real-time finance use cases.
Microsoft provides solutions that fit within their broader ecosystem of tools and product strategy. These tools are strong for the general use case, but not strong for real-time finance use cases.
Why hasn't Microsoft built the same real-time feed?
Could Microsoft block this later?
Highly unlikely. Removing deployable packages would break hundreds of ISV solutions. API changes carry 12-24 months' notice.
Highly unlikely. Removing deployable packages would break hundreds of ISV solutions. API changes carry 12-24 months' notice.
Could Microsoft block this later?
Will it impact D365 performance?
Queries run NOLOCK as low-priority batch jobs. If D365 auto-kills the job to protect performance, Zap resumes from the last processed partition, and the UI threads stay unaffected.
Queries run NOLOCK as low-priority batch jobs. If D365 auto-kills the job to protect performance, Zap resumes from the last processed partition, and the UI threads stay unaffected.
Will it impact D365 performance?
How are deletes handled?
We copy posted rows only. Hard deletes are reconciled via a scheduled partition reload (weekly default, nightly optional).
We copy posted rows only. Hard deletes are reconciled via a scheduled partition reload (weekly default, nightly optional).
How are deletes handled?
Query pattern & indexing?
Single-table reads or header/line joins on timestamp. Ad-hoc SQL not supported. All modelling is performed in the warehouse. Zap flags a few one-time indexes for high-volume tables.
Single-table reads or header/line joins on timestamp. Ad-hoc SQL not supported. All modelling is performed in the warehouse. Zap flags a few one-time indexes for high-volume tables.
Query pattern & indexing?
Can we still use Fabric or Synapse?
Yes. Zap can source from Fabric or Synapse as an alternative when needed. We default to X++ to significantly reduce latency and setup.
Yes. Zap can source from Fabric or Synapse as an alternative when needed. We default to X++ to significantly reduce latency and setup.
Can we still use Fabric or Synapse?
Roadmap?
Upcoming release adds entity-key back-mapping for quicker delete detection.
Upcoming release adds entity-key back-mapping for quicker delete detection.
Roadmap?
Docs and real humans!
-
In-app, context-specific doc navigation
-
Also available at docs.zapbi.com
-
Hover over elements for tooltips and quick links
-
In-app scheduled weekly ask-me-anything's (AMAs)
-
Mentoring available on-request
In-app training video platform
-
Filter by difficulty, topic or status (unwatched and more)
-
Use picture-in-picture mode for seamless side-by-side guidance
-
Navigate quickly with jump-to-chapter functionality
D365 F&SCM
Connectivity FAQs
D365 F&SCM
Connectivity FAQs
Get trusted D365 F&SCM data without the bottlenecks
Zap's X++ extractor delivers Dynamics 365 F&SCM teams near-real-time data loads without throttling production. The FAQ below breaks down how it works, why OData/BYOD/Fabric exports fall short for the month-end close, and answers key questions about performance, delete capture, and roadmap.