Forum Discussion
Power Bi Paginated Report preview visibility issue
I've designed a report, and when I preview it, the value fields aren't visible. However, when I export the report to Excel or print preview it, all fields display as expected. Is this a bug, or have missed some display setting?
Hi SteveD2
Tthis is almost always an HTML/interactive renderer issue (the preview uses HTML5), not your dataset or tablix logic. Excel export + Print Layout use different renderers, so they can look “correct” even when the interactive preview doesn’t.
Things to check (in this order):
Report Properties → InteractiveSize
In Report Builder: Report Properties → Interactive Size
Make the InteractiveWidth at least as wide as your tablix (or set it to 0 to avoid soft page breaks in interactive viewing).
If InteractiveWidth is smaller than the tablix/body, the HTML preview can “paginate/clip” content in weird ways.
Body width vs Page width
Ensure the Body width is not larger than what the viewer can render without breaking.
Even if PDF/Excel handles it, HTML preview can clip the “right side” (exactly like your screenshot).
Any Visibility / Color expressions
In the problematic cells, verify:
Color isn’t evaluating to white/transparent in HTML
BackgroundColor / conditional formatting isn’t wiping it out
Visibility → Hidden isn’t driven by an expression (especially anything using Globals!RenderFormat.Name)
Overlapping objects (rectangles/images)
In the design surface, it’s common to have a rectangle/background sitting on top of the tablix.
Exports can render Z-order differently than HTML.
Use the selection pane (or click around the blank area) and Send to Back anything that could be covering the tablix.
Column group page breaks
If you have page breaks on column groups (months/periods), HTML preview might be pushing the values to the next “soft page”.
Check column group properties for PageBreak settings.
If he can share whether this is Power BI Service paginated report preview or Report Builder preview, and a screenshot of Report Properties (PageSize + InteractiveSize), you can pinpoint it fast.If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
3 Replies
- Ritaf1983
Super User
Hi SteveD2
Tthis is almost always an HTML/interactive renderer issue (the preview uses HTML5), not your dataset or tablix logic. Excel export + Print Layout use different renderers, so they can look “correct” even when the interactive preview doesn’t.
Things to check (in this order):
Report Properties → InteractiveSize
In Report Builder: Report Properties → Interactive Size
Make the InteractiveWidth at least as wide as your tablix (or set it to 0 to avoid soft page breaks in interactive viewing).
If InteractiveWidth is smaller than the tablix/body, the HTML preview can “paginate/clip” content in weird ways.
Body width vs Page width
Ensure the Body width is not larger than what the viewer can render without breaking.
Even if PDF/Excel handles it, HTML preview can clip the “right side” (exactly like your screenshot).
Any Visibility / Color expressions
In the problematic cells, verify:
Color isn’t evaluating to white/transparent in HTML
BackgroundColor / conditional formatting isn’t wiping it out
Visibility → Hidden isn’t driven by an expression (especially anything using Globals!RenderFormat.Name)
Overlapping objects (rectangles/images)
In the design surface, it’s common to have a rectangle/background sitting on top of the tablix.
Exports can render Z-order differently than HTML.
Use the selection pane (or click around the blank area) and Send to Back anything that could be covering the tablix.
Column group page breaks
If you have page breaks on column groups (months/periods), HTML preview might be pushing the values to the next “soft page”.
Check column group properties for PageBreak settings.
If he can share whether this is Power BI Service paginated report preview or Report Builder preview, and a screenshot of Report Properties (PageSize + InteractiveSize), you can pinpoint it fast.If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
- V-yubandi-msft
Community Support
- V-yubandi-msft
Community Support
Hi SteveD2 ,
We haven’t received a response from your end yet. Please let us know whether the issue has been resolved or if you’re still facing any difficulties. Feel free to reach out if you need further assistance.
Thank you.