The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hello, Community,
I have a problem with paginated reports. I created the reports on desktop application, and it works correctly on PowerBi Desktop application.
However I pusblised the report to service, and the paginated report can not be rendered.
It seems for a few seconds it is loading, then I get the following message.
It is not about authorition or accessing the report, because from my own account (I am admin) can see.
Sometimes when i click a few times on the report (which applies filters) it can be rendered. But sometimes I can not render.
I think it is something about timeout or something?
I read I can read gateway logs somewhere, but I can not fint where to read it.
I have Power BI premium per user, the viewers have PRO license. (the report and the paginated reports are in PRO workspace)
Here is the error message: Thanks for anyone who can help.
---------
Unable to render paginated report
We’re sorry, we ran into a problem while running the report. Please try again later.
Object reference not set to an instance of an object.
Timestamp: 2023-08-07T12:44:42.085Z
Root activity ID: 34bee385-d2c3-43f1-859a-d04e6fb1bee8
Session ID: 00004ba447cb4917a661888ed5e86f58
Tenant ID: undefined
Cluster: https://wabi-west-europe-e-primary-redirect.analysis.windows.net/
Report ID: 97404b3f-da89-4141-a9c3-895e41ac9faa
ReportViewerVersion: undefined
Solved! Go to Solution.
Object Ref exception is unexpected. You have Premium and Pro license, you can file a support request with this information to get this resolved.
Hello,
First try to delete the parameters from paginated report. If it works in this case, the problem is with the parameters.
Regards
Greg
Object Ref exception is unexpected. You have Premium and Pro license, you can file a support request with this information to get this resolved.
Thank you Bradsy,
I contacted them, and the problem was solved.
Let me write here the solution, maybe it is usefuly for someone.
The problem was the filter applied to the paginated report. when I removed the parameters from the paginated report, it worked well in the service too (without any filter)
Solution: I created a measure and got the data . filter_measure = selectedvalue(Company_code) for exapmle. If I click on some company on the page, this measure gets the company's name/code or whatever. I put this measure to the paginated report's parameters, and it worked in desktop and service too.
Hope it helps for someone.
I'm facing similar issue but i'm having issue in power bi desktop. Could u explain a little bit how to resolve this?
User | Count |
---|---|
38 | |
14 | |
12 | |
11 | |
8 |
User | Count |
---|---|
49 | |
35 | |
22 | |
21 | |
18 |