Integration between Dynamics 365 Finance & Operations (D365 F&O) and Microsoft Fabric

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

• Change tracking

• Data entities

• Fabric pipelines