Forum Discussion
Custom Report Size to Dashboard
BrianPDX I would just create a quick "pointer" element on the dashboard so the user has to click it to be taken to the report. For example. this could be as simple as creating a text box with "Premanage Report" - pin that to the dashboard, and delete it from the report page. The pinned visual on the dashboard will still take you to the report page.
Or, you could get fancy and do the same with an image or snapshot of the report or an element.
Either way, rather than fight the behavior of dashboard tiles, my suggestion is to just get people to navigate to the actual report as efficiently as possible.
BrianPDX I just re-tested this. Place the visual, pin it, save the report.
Re-open report, delete the visual - the tile will still be there.
You're right it worked.
For some reason when I create a textbox visual via the web app and delete it, the tile gets deleted. When I made the visual via the desktop, your work around worked just fine.
I'll go ahead and mark this as "solved" but if anyone has another other suggestions, I'd like to hear them. I'm just trying to make the process as easy as possible for end users (upper management) as they are not tech savvy at all.
Hi Brain,
you got the solution .. ?
am unable to get the point.
could please help me on this.
Thanks & Regards,
vinod
Hi,
This is still an issue. I created a report with two sheets (resolution 1920 x 1080) with a slicer on each sheet (which refers to the same field). The customer wants to use the slicer once, so I put sheet2 under sheet 1, creating a page with a resolution of 1920 x 2160. Now the slicer affects the entire report, letting the customer use it once and scroll through the entire report. When publishing this report, all seems well, untill a pin it as a live page to a dashboard, which results in a page with a white border on both sides:
It looks like Power BI is (in this case) auto-adjusting the width when i pin the page on a dashboard, which seems like a unintentional action to me. Any thoughts on this? The suggested pointer is not really a solution, but rather a workaround.
Hi,
Is there a solution for this?
Thanks,
Dan
