Pixel width was set on the macro but the report still fills the whole column
What you are seeing
A pixel width was set on the macro but the report still fills the whole column.
#Why it happens
A configured width is treated as an upper bound and clamped to the page column width. This is deliberate. The original Connect app hardcoded the frame to full width, and an unclamped pixel width could push the frame past the column and drag the whole Confluence page sideways.
#What to do
Widths narrower than the column do apply. If the report still looks full-width, the value entered is larger than the available column, so reduce it.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Power BI global settings entry | Confluence admin - Apps - Power BI | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Maximum frame width | 100% of the page column | A configured pixel width is capped at the column width. |
Licensing | Macro declares unlicensed and anonymous | The macro frame still renders for unlicensed and anonymous readers; whether they see the report depends entirely on Power BI's own access rules. |
#A few things that catch people out
Configured width is a ceiling, not an override. The frame is clamped to the page column so a wide value cannot drag the Confluence page sideways. This differs from the old Connect app's behaviour.
#Related
Scrolling the Confluence page stops when the mouse is over the report; the first click on the report
An invisible 'Click to interact' overlay sits over the report so page scrolling is not cap
Someone types a lookalike address such as app.powerbi.com.example.net and the macro appears to accep
After the strict checks fail, there is a final loose fallback that tests whether the hostn
Everything else
The rest of this family.
Found it? Good.
