Forum Discussion
Super UserIntegration between Dynamics 365 Finance & Operations (D365 F&O) and Microsoft Fabric
Hi everyone,
We configured the integration between Dynamics 365 Finance & Operations (D365 F&O) and Microsoft Fabric about two years ago. The synchronization has generally been working, but we recently noticed a data inconsistency.
In D365 F&O, there are two records present in a specific table, but these records do not appear in Microsoft Fabric. It seems that during the synchronization process, these records were not transferred or were dropped.
We would like to understand:
- Why would Microsoft Fabric skip or drop records during the sync with D365 F&O?
- Are there known scenarios where records might not be synced (e.g., incremental sync issues, filters, data validation, or failed pipeline runs)?
- Is there a recommended way to identify missing records and re-sync them ?
Additional context:
- The integration was configured approximately 2 years ago.
- Only two records are missing, while the rest of the data appears correctly in Fabric.
- We are trying to determine whether this is due to incremental refresh logic, sync failures, or data filtering.
- Any guidance on troubleshooting this would be greatly appreciated.
Thanks in advance.
Hii MohdZaid_
Microsoft Fabric itself does not randomly drop records, but missing rows usually occur due to incremental refresh logic, filters, failed pipeline runs, or data validation issues during synchronization. If the integration uses incremental loading (based on modified date or watermark), records with older timestamps or incorrect values might be skipped.
To troubleshoot, first check the pipeline or dataflow run history in Fabric to see if any runs failed or partially loaded data. Then verify whether filters, security rules, or incremental load conditions are excluding those records. The most reliable fix is to run a full refresh or reprocess the affected table/partition so Fabric reloads the missing records from Dynamics 365 F&O.
Hello MohdZaid_,
Microsoft Fabric normally does not drop records during ingestion. When integrating Microsoft Dynamics 365 Finance & Operations with Fabric, missing rows are usually caused by the synchronization mechanism, not Fabric itself.
Common causes
Incremental sync / change tracking – Records created before tracking was enabled may not be captured.
Entity or query filters – Filters on legal entity, status, or company may exclude records.
Pipeline ingestion issues – Partial failures or delayed retries.
Schema/validation errors – Row-level constraints may block ingestion.
Fabric-specific scenario – Records may exist in the lakehouse but appear missing due to incremental partitions, filters, or delayed ingestion. Query the raw table by primary key to confirm.
Docs
4 Replies
rohit1991Hii MohdZaid_
Microsoft Fabric itself does not randomly drop records, but missing rows usually occur due to incremental refresh logic, filters, failed pipeline runs, or data validation issues during synchronization. If the integration uses incremental loading (based on modified date or watermark), records with older timestamps or incorrect values might be skipped.
To troubleshoot, first check the pipeline or dataflow run history in Fabric to see if any runs failed or partially loaded data. Then verify whether filters, security rules, or incremental load conditions are excluding those records. The most reliable fix is to run a full refresh or reprocess the affected table/partition so Fabric reloads the missing records from Dynamics 365 F&O.
- Olufemi7
Hello MohdZaid_,
Microsoft Fabric normally does not drop records during ingestion. When integrating Microsoft Dynamics 365 Finance & Operations with Fabric, missing rows are usually caused by the synchronization mechanism, not Fabric itself.
Common causes
Incremental sync / change tracking – Records created before tracking was enabled may not be captured.
Entity or query filters – Filters on legal entity, status, or company may exclude records.
Pipeline ingestion issues – Partial failures or delayed retries.
Schema/validation errors – Row-level constraints may block ingestion.
Fabric-specific scenario – Records may exist in the lakehouse but appear missing due to incremental partitions, filters, or delayed ingestion. Query the raw table by primary key to confirm.
Docs
v-kpoloju-msftCommunity Support
Hi MohdZaid_,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to Olufemi7, rohit1991, for those inputs on this thread.Has your issue been resolved? If the response provided by the community member Olufemi7, rohit1991, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.- v-kpoloju-msft
Hi MohdZaid_,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.Thank you.