We have created a filled map using the names of some places in The Netherlands. My collegua created this filled map and then it worked fine in Power BI Destop (June). Then we published it to our SSRS portal and the filled areas on the map were only patially loaded. When I open the map in different versions op Power BI desktop I also get a fastly different result then my collegue.
We already set our system language to "English" USA. This solved some of the misplacements but definitly not all.
I though this was fixed in the last release and seemed to stopped happening after I downloaded the newest version. Now it is back and is a complete pain to deal with. Please fix this issue.
I'm getting this error since yesterday on a new dataset. It is a simple excel file table. I've done the following.
Signed out of Power BI Desktop and back in
Got the latest personal gateway
turned the gateway service off / on
republished multiple times during this process.
Others seem to be having the same issue. see thread here
There is a current support site error message, but it is specific to SharePoint as a data source only.
The result of: Record.ToTable(#sections[Section1]) are returned correctly in the query editor, but not loaded to the data model. There, only the value of the current query will be returned.
In Excel, this works fine, so both results are the same: A table with all queries in the current file.
We can use the new matrix visual which provide drill down with the March 2017 through June 2017 releases of Power BI Desktop. I created one report with these visuals in Power BI Desktop and can open it with Power BI Desktop RS(June). Unfortunetely, when ı try open deployed report in Power BI Report Server matrix visuals appears as blank visuals. Besides Power BI Desktop RS hasn't preview features in options so ıt doesn't support new matrix visuals and default matrix is not new version. As far as ı know , Reporting Server will upgrade quarterly .When will Power BI Desktop RS support these visuals?
I raised a bug that I thought was fixed in the new version of Power Query, but it has since reoccurred.
Do you know what could be the cause of or solution to this?
We are trying to use Power BI to pull data from SAP BW leveraging both BEx queries and cube connections. With each scenario we are running into different issues and were trying to figure out if this is a Power BI Limitation/Issue with 1. Connecting to a Warehouse 2. They way that Power BI is communicating with SAP BW to pull its data or is this a SAP BW Limitation/Issue based on how SAP BW servers up data.
Tested With Cube:
0FIGL_C10 -General Ledger (New) Transaction Figures
Data Load is very slow
Adding new columns and refreshing data seems to take a very long time. I don't know if this is a sap warehouse issue, an OLAP issue, or a power bi Issue. I had our basis team monitor our BW environment when connecting to a cube where I selected all the columns. The cube contains 349,628 records which is based on generating the SQL Statement from the cube (In SAP BW RSA1) and executing that in SQL Server Management Studio. This call eventually failed with the following ‘RFC_ABAP_RUNTIME_FAILURE: TSV_TNEW_PAGE_ALLOC_FAILED which I was told was due to running out of memory. Prior to testing this I had Basis increase our memory footprint on the server in an attempt to rule out memory issues.
Column limitation (selecting to many columns) or possibly and combination of Columns + Rows
When I connect to a cube and select 1-4 fields everything is pretty responsive. But as you start adding more and more fields the performance starts to suffer. In testing it looks like we can add 12 fields without any issue (Super Slow Refresh Times) but once we hit the 13th field we get an RFC_ABAP_RUNTIME_FAILURE – TIME_OUT.
I don’t write a lot of MDX statements so my statement could be the cause of the issue but I run into the same issues remain. Which makes sense because I believe Power BI is connecting to SAP BW through the BW Open Analysis Interface OLBAP BAPIs regarless of if you going againt a Cube, BEx Query, or MDX.
Select NON EMPTY [Measures].MEMBERS ON COLUMNS, NON EMPTY [0FISCYEAR].Members * [0CO_AREA].Members * [0COMP_CODE].[LEVEL01].Members PROPERTIES [0COMP_CODE].[20COMP_CODE] on rows from [$0FIGL_C10] WHERE ([0COMP_CODE]., [0FISCYEAR].[K12016])
Select NON EMPTY [Measures].MEMBERS ON COLUMNS, NON EMPTY [0FISCYEAR].Members * [0CO_AREA].Members * [0COSTCENTER].Members * [0CHRT_ACCTS].Members * [0CO_AREA].Members * [0CURTYPE].Members * [0FUNC_AREA].Members * [0GL_ACCOUNT].Members * [0PROFIT_CTR].Members * [0SEGMENT].Members * [0VALUATION].Members * [0VERSION].Members * [0FISCPER].Members * [0FISCPER3].Members * [0FISCVARNT].Members * [0FISCYEAR].Members * [0COMP_CODE].[LEVEL01].Members PROPERTIES [0COMP_CODE].[20COMP_CODE] on rows from [$0FIGL_C10] WHERE ([0COMP_CODE]., [0FISCYEAR].[K12016])
Key and Text Values
The last think I want to touch on is the key values. Power BI does not appear to give you the ability to select or toggle between the text and key values. Though MDX I was able to include the properties section and include the key value (Which was nice) but this should be standard functionality.
I wanted to try and cover all my bases and rule out as much as I could to try and pin point the issue. As such I used Tableau to connect to the same structure as it’s my understanding that it also utilizing the BW Open Analysis Interface OLBAP BAPIs to query SAP BW. I’ll point out that I don’t really use Tableau but it was a tool that was available to use a test. Once again I had Basis monitor the SAP Environment to help track down any issues. Within seconds tableau had pulled in the Metadata and I was able to create a sheet. Tableau appears to provide a live query connection to the cube whereas Power BI appears to try and load the data first which may also be contributing to the performance issues. Again I just wanted to test with another tool to try and rule out the SAP environment.
With SAP being our ERP system we need the ability to effectively be able to query our data warehouse and provide the user community with self-service reporting/analytics. With the issues listed above its making this a very difficult process to move forward with. Any ideas or suggestions would be greatly appreciated. We love Power BI and the users who have seen our demos love what it can do and I feel like we are always installing this on someone’s machine.
Here are a couple ways to get the error:
- Open the dashboard via the initial login screen
- Open the dashboard via the workspace
When the dashboard is clicked I experience the following behaviors:
The first option you get this (a) error message and once you click through it several times you finally get to the dashboard and it does not have correct color scheme - should be #A6093D (b), also the name in the IE tab does not match the dashboard name (c). See images
When I go through the workspace to get to the dashboard, I don’t get (a) or (c) from above but I get (b)
I've got a site report that I use url paramaters to direct users to a specific site, based on the site code. this works in "My" Workspace
However, when I publish the exact same report to an App Workspace, the URL filters fail.
The report comes back non filtered, and I can see the url parameter being removed from the URL. I've tired a couple of reports with the same behaviour. Can we not use URL filters on app workspace reports?
Can anyone replicate and confirm it's not just me?
In the new January, 2017 release, I get a "Report has already been published" error message when I try to use the PUBLISH option to Update a report that exists on the Service from Desktop.
--I updated a report in Desktop that had been previously published to the Service.
--I selected the PUBLISH menu option in Desktop
--I selected MY WORKSPACE (where the report was located)
--I received an error "Report has already been published" and the update failed.
I've tried with several different reports both with the Service running and with the Service not running. I've also exited Desktop and restarted it and repeated the operation. In all cases, I got the same error.
When we run PowerBI Version: 2.46.4732.581 64-bit (May 2017) and connect to a SAP Hana 2.0 everything works fine and you can see the Calculation Views listed in the Navigator.
When we run the latest download July it can connect to a Hana 2.0 database but we do not see the list of Calculation views in the Navigator.
Both builds are fine for Hana 1.x databases.
Using Hana 2.0 64 bit ODBC driver.
When changing the formatting in a text box it will often exhibit erratic behavior. The section that you highlight (to change font, size, color) will come un highlighted. When changing to a custom color after typing the first 3 characters of the html color code it will unhightlight the selection and change you to typing in the box where your text is located. Often fonts will revert back to system standard without being touched by the user.
I have two accounts, one paid pro, the other a trial pro account. Come June 1st and my gateway is offline and not able to reconnect ot the service?
Here is the message I get in my gateway: "Please wait while the gateway connects to the serivce"
We have an issue that our PBI file works fine but when row level security is turned on we get error messages.
We have tracked it down to a caculate measure. When row level security is off this measure works fine -
CALCULATE (sum(UnitSalesValues[Sale Values]), 'UnitSalesValues'[Attribute]= "Sold prior to qtr" )
When row level security is turned on this measure creates the following error is the visual. If the bolded part is taken out the measure works fine.
Colukn't load the data for the visal
An unexpected exception occured.
This same file was working with last months version of PBI. The data in UnitSalesValues is visable with the row level security turned on and has values for "sold prior to qtr".
However, even if we use last months pbix file it does not work in the PBI Embeded enviroment.
This certainly seems to be an error in PBI. Further when the row level security is first turned on a black screen apears and the following program is run.
c:\Program Files\Microsoft Power BI Desktop\bin\SQLDUMPER.EXE
Since yesterday I'm having an issue connecting to an excel file in a Sharepoint folder. It was already working, but I made some changes and republished it. Refresh works fine in Power BI Desktop, but online. It seem it's trying to connect to a Sharepoint list, instead of folder. I have an other report connecting to an other excel file in the same folder and it works fine. Could this be connected to the issue in North Europe? I'm in that datacenter.
There's a bug in "Don't include in report refresh" like described here: http://community.powerbi.com/t5/Desktop/Disabling-quot-Include-in-Report-Refresh-quot-works/m-p/1017...
unfortunately I didn't test correctly and this thread is closed, but the bug is still there and preventing solutions for problems like this:
If the query that shall not be refreshed is not referenced by any other query or part of a UNION-operation in DAX, then everything works fine, but if it is referenced as mentioned, then it will be loaded again.
A lot of the usecases for this features are of this kind, so this bugfix is really needed !!!
Slicer correctly filters matrix to empty in desktop; matrix in web version retains previous contentsStatus: Needs Info
Slicer correctly filters matrix to an empty set in the July 2017 desktop version.
In the published web version, the sliced matrix incorrectly retains pre-slice contents, seems to ignore slicer.
Slicer field is in fact table.