I’m managing a series of executive dashboards that use a Live Connection to a centralized Power BI semantic model. Lately, the page navigation feels sluggish, and visuals are taking several seconds to render. Since I can’t edit the underlying data model or use Power Query in this mode, what are the best strategies to "clean up" the report side? I need advice on reducing visual overhead and optimizing report-level measures to improve the end-user experience.
3 answers
When dealing with a Live Connection, your optimization power is concentrated on the report canvas. The first step is to use the Performance Analyzer to identify which visuals are the bottlenecks. Often, the delay isn't the data source but the "Visual Display" time. To clean this up, reduce the number of visuals per page; aim for a maximum of 8-10. Every visual, including slicers and cards, sends a separate DAX query to the underlying model. I also recommend replacing multiple single-value cards with the new Multi-card visual to reduce the query count. If you’ve created complex report-level measures, try to simplify them or ask the dataset owner to move them into the core model to take advantage of server-side caching.
Don't forget to check for hidden visuals or heavy background images. Using a high-resolution image as a background can increase page load time more than you'd think.
That makes sense for the visuals, but what about slicers? In a Live Connection, every time I click a slicer, every other visual on the page refreshes. Is there a way to stop that "chatter" without losing the interactivity our users expect
Great point, David! You should definitely use the Query Reduction settings found in the Options menu. You can add an "Apply" button to slicers so that queries are only sent once the user has finished making all their selections. Also, check your Visual Interactions. By default, every visual filters every other visual. If you have a chart that doesn't need to be filtered by a specific slicer, turn off that interaction. This prevents unnecessary DAX queries from being sent to the Analysis Services engine, which significantly lowers the load during high-traffic periods.
I agree with Sarah. I once found a report where the developer had hidden dozens of visuals behind shapes instead of deleting them. In a Live Connection, those "hidden" visuals still trigger queries! Cleaning those up and using the Selection Pane to manage visibility properly is a quick win. I'd also suggest using Sync Slicers sparingly, as they can add background processing overhead to pages you aren't even looking at.