Sometimes when I use the dropdown slicer in Power BI Desktop, the list of values doesn't disappear after clicking out of it. It will stay on the screen even if I go to a different page of the report.
The only way to "fix" it is save my report and reopen the report by closing Power BI Desktop.
Please fix as soon as possible, thanks.
I have several text tiles on my Dashboard. I made some changes to the text content and styling and saved them, and the save appeared to work. However, when I navigated away from the dashboard and returned to it, the changes had been reverted. I checked with collaborators and no one else had even been on that dashboard at that time.
I tried to add "column from example" in Power BI, which worked so great, but I think I found a bug about it. I did that by inserting the step, so that add column from example is not the last step, however, the M code generated put it to the very last step, and worse it replaces the last step. The title step is still the one I created, for example: Removed Columns, but the code of add column from example was put there.
Power BI Desktop Version: 2.42.4611.701 64-bit (January 2017) Installed today.
Login window blocked by "Working on it" spinner popup after Power BI Desktop idle in background for a bit. I didn't nail down the time but both times it was over 20 minutes. The login expires after an indeterminate amount of time of inactivity, over 20 minutes at least. Clicking publish brings up the login window but is behind the "Working on it..." popup.
I have to end the task, open Power BI, click login up in the top right corner, then I can publish.
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.
Not sure if this is related to the data refresh issue, but starting yesterday I have two different external customers (both in California) that view different dashboards. They are able to get to the dashboard frames, however get an error stating that "something went wrong.. unable to load the data model".
Anyone else experienceing this with external users?
Our data is on prem, we use the personal gateway, and the external customers are using the link provided in the original MSFT email I shared with them.
I have dashboard that links to a report with 5 tabs. I have shared this dashboard with users both within my orginazation and outside of it. I have been having issues with users (both internal and external) not seeing all 5 tabs. They are only seeing 2 of the tabs.
I have tried removing their access, and then regranting access and sending them a new link, but that does not solve the problem. They have logged out and logged back in but that does not solve the problem. They have tried accessing the dashboard from the share dashboard URL, the URL in the invite email, and by logging in direct to app.powerbi.com and then navigating to their dashboards, but these do not solve the problem.
This is a bug, and was suggested to be logged here by @mihart from this forum post:
Details are on creation of a dashboard text box, with no links to reports. If you save the text box and then go to edit the text box, you are able to edit it with success, until you refresh the dashboard or file, at which time the updated text dissapears and the text box reverts back to it's original content.
In short, text boxes are not retaining content when an edit is made.
Have a date slicer in Power BI desktop, works as expected. Publish to service and two differences noted in behavior:
1) When hovering over the header, I no longer have control over the type of slicer to show, BETWEEN, BEFORE, AFTER, etc.
2) Tried to pick a single date while in between mode; 2/16/2017. Works as expected in PBI desktop, in service, I pcik 2/16/17 for start date, then pick 2/16/17 for end date and control automatically switches to 2/20/17????
Anyone else experience this?
I've been working on a data set for a few weeks that maps the top 10 records by zip code in the Map vizualization. This data set was working up until yesterday (2/13/2017). Today, 2/14, the power bi embedded version no longer maps the zip code data.
I downloaded the Feb 2017 power bi desktop update, and now I have the same problem in the desktop version. I went back to the January update - but the mapping there is also not working.
Did something break in Power BI? Or bing maps?
Please help, as this problem will completely derail a customer initiative.
I want to use a PNG as background with size 1600/900 for a dashboard. This image has only outer borders (see image). When I select this image in PBI Desktop as a background image, it does not show up on the canvas. Changing the image fit does not change this behaviour. It is probably there, but just seems out of bounds. After publishing the dashboard, the image shows perfectly in the PBI Service. Is it me failing or Power BI Desktop?
My main report has black background and white text. When trying to create a mobile view of the report in Phone Layout, I cannot set the background color I want and this causes the text to disappear vs. the default white background, when viewing it on the phone.
Please add functionality to control the background color in the Phone Report Layout view.
We have production implementation of Power BI, which contains various charts that have an interaction of slice set. Since the latest Power BI release, when clicking on a part of the bar graph in one chart all the bars/parts of the entire sibling chart becomes filled with the same value.
Notice that the 17K red portion of the chart on the left for 2017 = 43% of the total. Clicking on the part of the bar yields:
I would have thought that the red 43% portion of the 2017 bar would be highlighted with no changes to the other bars/parts.
Going back and using the January, 2017 release I get this:
OBviously this interaction is not very valuable and I could just turn off interaction for these charts but there are other charts on the same report that are also not slicing correctly.
We are using Compatibility level 1200 for the tabular model, so SSAS 2016. This is just a numeric attribute and the aggregation we are using is Median.
Power BI Desktop seems to be signing me out of my Power BI account. When I go to publish a report while not signed in it asks me for my credentials, but doesn't allow me to type anything in. I have to open Task Manager and Force Close Power BI, reopen, Sign In, then publish.
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.
On the video posted at https://powerbi.microsoft.com/en-us/documentation/
But, in the latest version of Power BI desktop (Version: 2.42.4611.901 64-bit (January 2017)), there is no such option for adjusting the text size. I need to be able to decrease the text size in the visual for a report I am creating.
Unable to cast object of type 'ComDataConvert' to type 'ComDataConvert'. The exception was raised by the IDataReader interface. The sync works perfectly on power bi desktop. Any help in this would be greatly appreciated.
I create a report on Power BI Desktop with a Project Online Odata feed as data source.
I can connect and update from PBI Desktop without any problems.
However, when i publish it to Power BI, and go to Schedule Refresh, i get this error under Data Source Credentials:
When i try to edit the credentials, i set to OAuth2 and enter the correct credentials but i got the error below:
I'm pretty sute that the correct authentication method to Odata feed is OAuth2, but i tried the other methods and got the same error
I'm not able to update the credentials in any situation. I've tryied to republish the reports, create a new one from scratch but i got always the same situation.