Forum Discussion
Helper VReport performance on fabric workspace
The issues you see are usually caused by a combination of capacity pressure, DirectQuery concurrency, view complexity, and query cold-start effects.
The “missing values” issue is often related to partial query execution, visual query cancellation, or timing issues with DirectQuery results, not data corruption.
You can replace the view with a materialized table, Reduce visuals per page if possible, and Check Fabric Capacity Metrics app for impact.
References that can help you :
Power BI DirectQuery limitations and performance
https://learn.microsoft.com/power-bi/connect-data/desktop-directquery-aboutPower BI performance optimization guidance
https://learn.microsoft.com/en-us/power-bi/guidance/power-bi-optimization
Super UserHi Hussein_charif,
This is expected as the service needs to wait for a query to return from the datasource before it can render a visual, and in the service there is more network latency as your datasources move through on prem gateways or through different datacenters around the world.
If you want to avoid the delay, I'd recommend moving towards using a Lakehouse or Warehouse to store your data, and using a DirectLake storage mode.