Views:

Applies to Product - Dynamics 365 Supply Chain Management


What’s happening?
The ingestion of Futures & Options (F&O) data to the Lakehouse is taking an excessively long time, particularly noted with the 'GeneralJournalEntry' table and other related tables.
 

Reason:
The initial sync of F&O tables to Fabric may take longer due to: - Large data volumes in the tables causing delays. - Performance bottlenecks in the data ingestion pipeline. - Inefficient data processing or transformation logic for F&O data. - Configuration issues with the Lakehouse or source system.
 

Resolution:

  1. Confirm the completion status of the initial sync for the relevant tables. For example, the 'GeneralJournalEntry' table's initial sync has been confirmed as completed.
  2. If the status of tables such as 'InventTransOrigin' shows "Not Created," advise the user to click the “Refresh Fabric tables” button to initiate the creation of these tables in Fabric.
  3. Engage the Dataverse team for further investigation if the creation is not initiated from the Dataverse UI.
  4. Check the telemetry logs for the sync process to identify any discrepancies in the expected completion times.
  5. If the ingestion is still slow, consider checking the capacity utilization metrics to ensure that the capacity is not being throttled due to high usage.
  6. If necessary, pause and resume the capacity to release accumulated usage, especially for F SKU's, to improve performance.
  7. For ongoing issues, ensure that the user is using the correct feature to create the Synapse link from Dataverse as per the documentation provided.