Forum Discussion
Power BI Table Scroll Glitch Across Desktop, Service, and Embedded Reports
Hi Power BI Community,
I'm encountering a frustrating UX issue with table visuals in my report.
I have four table visuals on the same report page. I’ve disabled all visual interactions between them using the Edit Interactions option. However, when I click on a field in one table, the scrollbars in the other table visuals start to flicker or jump slightly — they expand and contract briefly, even though there’s no data interaction or filtering.
This issue only happens when the tables have 20 or more columns. When there are fewer than 20 columns, the behavior does not occur.
This problem occurs across:
- Power BI Desktop
Power BI Service
Embedded Power BI report on a website
I’ve tried the following:
Disabling all visual interactions
Increasing padding between visuals
Locking visual size and position
Turning off responsive settings
Despite all this, the issue still persists. It seems related to rendering and scroll management when visuals have many columns.
Is this a known bug, or is there any workaround to stop the scroll flickering or jumping behavior?
Appreciate any help!
Thanks,
Sandeep
Hi sandeep07 ,
Thank you for reporting this issue and for providing a detailed summary of your observations and the troubleshooting steps you’ve already taken.
Based on your explantion, this appears to be a visual rendering behavior triggered when multiple table visuals with a high number of columns (20+) exist on the same report page. While visual interactions are disabled, the Power BI engine may still process layout recalculations behind the scenes when a selection is made, especially if visuals are tightly aligned or require horizontal scroll management.
As of now, this specific flickering behavior is not documented as a known bug, but we understand it can significantly impact user experience, particularly in embedded or service scenarios.
- As a workaround, consider reducing the number of visible columns in each table visual, or breaking them into separate pages where feasible.
- Enable "Performance Analyzer" in Power BI Desktop to ensure there's no unexpected processing triggered on selection that may be contributing.
- If possible, test with Matrix visuals instead of Table visuals to see if rendering behavior improves with the same dataset.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
5 Replies
Hi sandeep07 ,
Thank you for reporting this issue and for providing a detailed summary of your observations and the troubleshooting steps you’ve already taken.
Based on your explantion, this appears to be a visual rendering behavior triggered when multiple table visuals with a high number of columns (20+) exist on the same report page. While visual interactions are disabled, the Power BI engine may still process layout recalculations behind the scenes when a selection is made, especially if visuals are tightly aligned or require horizontal scroll management.
As of now, this specific flickering behavior is not documented as a known bug, but we understand it can significantly impact user experience, particularly in embedded or service scenarios.
- As a workaround, consider reducing the number of visible columns in each table visual, or breaking them into separate pages where feasible.
- Enable "Performance Analyzer" in Power BI Desktop to ensure there's no unexpected processing triggered on selection that may be contributing.
- If possible, test with Matrix visuals instead of Table visuals to see if rendering behavior improves with the same dataset.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Hi sandeep07 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @sandeep07 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.Hi sandeep07 ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi Anonymous,
Thank you for your valuable response to my query in the community. I have raised a ticket with the Microsoft team, and they have acknowledged it as a bug. They informed me that it will be fixed in an upcoming update, hopefully soon.
Thanks again for your support.
