Run Power BI Desktop as administrator before opening the report.
Recently, when opening a report from Power BI Report Server that used a SQL database as a data source I received the following error.
An error happened while reading data from the provider: ‘Could not load file or assembly ‘System.EnterpriseServices, Version=22.214.171.124, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. Either a required impersonation level was not provided, or the provided impersonation level is invalid. (Exception from HRESULT: 0X80070542)’
So I clicked “Edit Queries” to see what was going on and received almost the same error but referencing a specific table and getting me thinking about SQL specifically.
So I checked that table in the query editor and received yet again the same error.
Simple solution. It’s likely that your credentials and queries are just fine.
The solution for my particular issue here, and the meaning behind the “impersonation level” part of the error, is just that you need to run Power BI Desktop as administrator before accessing the report. After opening the report in Power BI Desktop being ran as an administrator, everything worked as expected.
Did you recently download a newer version of Power BI Desktop (optimized for Report Server)? The latest is August 2018 as of the writing of this post. If you’ve downloaded August and are trying to save to an outdated version of Report Server via the client application, it’ll give you this error message.
“An error occurred while attempting to save the report to Power BI Report Server.”
And you can try going to Power BI Report Server via your browser and uploading there directly, but you’ll get this error message which is more helpful:
“We can’t save this Power BI Desktop report because either it is newer version or has component parts that are not supported.”
This error occurs when users are trying to save a report from a Power BI Desktop version that’s newer than the version of Power BI Report Server installed on your server.
Upgrade your Power BI Report Server version to the latest available to make sure it’s compatible with users using the latest version of Power BI Desktop available. It will be backwards-compatible in case you have users still on October 2017 or March 2018.
Log in to the server that hosts your Power BI Report Server
Download the latest version of Power BI Report Server
Go to https://powerbi.microsoft.com/en-us/report-server/
Click “Advanced download options”
Select your language and click “Download”
Check the box next to “PowerBIReportServer.exe” and “Next”
Run the downloaded .exe file and click “Upgrade Power BI Report Server”
Follow the prompts, and reboot the server when finished. This will cause a short amount of downtime.
You should now be able to access and save reports from/to the server as usual from all versions of Power BI Desktop.
RELATED() pulls values from different tables based on relationships established in the relationships tab. This is useful and makes it so we don’t necessarily need to append or merge tables to get the same result.
For example, we can create a new calculated column in our fact table Sales that pulls in related information from two other tables without needing to append or merge tables:
Power BI tries to be helpful and auto-detects data formats such as dates, decimal numbers and integers. However if you’re dealing with zip codes, employee IDs, product IDs, etc. that have leading zeroes, you may not want them auto-converted to integers/number format which removes the leading zeroes. Here’s how to get them back.
From Power Query Editor (recommended)
Click the “Data type” icon next to the column name
From Data Tab
Select the column header
From the Modeling tab, change “Data type” to “Text”
In Power BI there are several custom visuals available, such as Elastacloud’s Calendar Visual, that show the density of events over time. However, if your data includes date ranges (start date with a different end date, such as task/project lists), visuals like these will only understand one of the two dates (whichever you’ve chosen for the data value) and none of the dates in between will be accounted for, making your data visualization incorrect.
You can, however, “expand” these date ranges or durations to create rows for all the dates including start, end and those in between. This way each date that’s part of the range is then graphed appropriately.
Did you know you can adjust the page size of your reports in Power BI? Each tab/page of your report can be a unique size specified by you down to the pixel. This comes in handy for creating “widget-like” visuals for embedding or for creating reports for print and optimal display on various screen sizes.
The following is a DAX formula you can use to create a calculated column that shows “next year’s” value in “this year’s” row. You can easily adapt this to show “yesterday’s” amount or “tomorrow’s” total as well. It can be modified for days, weeks, months, etc. as long as the time measure is able to be sorted sequentially.
Power BI Report Server (as of the time of this post) doesn’t allow preview features, therefore doesn’t allow custom themes (easily). But with a little work, anyone can easily “install” a custom theme for their report in PBIRS in just a few steps.