A few days ago, my slicers layout got ruined: because its not possible to configure font and background color for either selected and unselected slices, we can only use force "default" colors for slicers.
I have a couple of horizontal orientation slicers. Dark grey as background color and white as foreground, right? Nope. Dark grey as background color, black as foreground color...
PowerBI Desktop - Dark Grey & white -> perfect
Published link (web) - Dark grey & black -> wrong
How can i solve this? Even better, when will we all be able to set colors for background and foreground (selected slices)?
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 !!!
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.
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.
So since today I've been getting one of following errors. It started when I tried to publish an existing version of a report, when i got this error.
The remote server returned an error: (404) Not Found.
Publishing failed for uknown reason
Endless "publishing", that cannot be cancelled and the powerbi must be shut down via task manager
Here is what I tried so far:
- removed the data set
- rename the report
- create a new report on same data set
- create a new report on different data set (and connection type)
- moving the .pbix file to online storage
- relog, restart, trial pro version, publish to workgroup
- and of course googling for hours.
EDIT: Looks like it was resolved, today it works fine.
The gateways seem to disconnect from the cloud account , trying to re insert them gives an error
"personal gateway sign in error: an unknown state error occurred Initial Response"
Could someone please advise ? ?
Is there an outage/service issue? Oragnisation wide we are unable to export data from any of the visuals (over 2000 reports).
This is the error for the past four hours.
Error exrpoting data.
Sorry, we couldn't export your visual data right now. Plesae try again
We like to use the Export to Powerpoint feature but I think we've found a bug. If I publish a report from PBI desktop to the PBI.com service and then export the report to Powerpoint it works fine. If in the PBI.com service I take a copy of that report to modify it (by using Save As and giving it a different filename) the export to Powerpoint produces blank slides for each page in the report. The report has no embedded images and only has 5 or 6 pages in the report. Please help - being able to export consistently to Powerpoint is a big part of our use of PBI. If it doesnt work we may have to stop using it. Of course we can take screen grabs of each page and paste them into Powerpoint but I wouldnt expect my users to have to resort to that approach. Thanks.
me and my collegues receive the following error message in Firefox 53.0.3 when we try to access the PowerBI App by the domain https://app.powerbi.com/
Secure Connection Failed An error occurred during a connection to app.powerbi.com. Invalid OCSP signing certificate in OCSP response. Error code: SEC_ERROR_OCSP_INVALID_SIGNING_CERT The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem.
This does not happen with Chrome or the Internet Explorer.
Please check the server certificate of this domain or report this issue to the responsible department.
Thanks and best regards,
When i click on See Records option from the Column Chart, i was able to go to the see records view
But, i am unable to export the data into excel.
I was able to see this option couple of days back
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.
This morning, when I started Power BI Gateway - Personal, it failed with the error, "GWConf has stopped working A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I uninstalled and re-installed the application but am still getting the same error. The Personal gateway as worked flawlessly for weeks prior to today. I'm not aware of any changes being made to my PC but I'm using a company computer and sometimes our IT department pushes out updates without prior notification. Where do I begin looking for the cause of the failure? (I'm just a Power BI user, not a developer.)
After upgrading the Personal gateway to the june version blank date fields gets imported as 1899 dates rendering my reports broken (since I filter on e.g deleted_at = blank).
Swithced back to older version (Apr release) returns import to normal behaviour.
This is an on premises scheduled refresh from an AWS RDS ProstgreSQL DB.
Any idea on how to correct this?
A few days ago i noticed that the colours of the highlighted filters become different afther being published. I've checked and the system is updated, including pbi desktop.
On the pbi desktop app this is how it looks a filter with the highlighted 2016:
After being published, the highlighted 2016 looks like this:
Somehow, all filters based on this visual in every dashboard have the same error, but the filter works.
Somebody turned off the SELECTION controls on the BI Cloud.
Attached capture shows a selection box. But if you click on the box, it no longer gets highlighted.
This is new. Whatever change was made only happened in the past few hours.
Can you please fix it?
I have several problems with map visuals in Power BI Desktop and Power BI Service:
- After several months of working with Power BI Desktop (I guess it's a matter of caching or/and upgrades) Filled Map displays only some part of voivodeships in Poland properly. Re-installation of Power BI Desktop and deleting cache folder help here, but it's annoying one (business user getting into %appdata% and deleting cache - can you imagine this scenario in production?).
- ESRI ArcGIS Map displays two voivodeships (pomorskie and kujawsko-pomorskie) in the same boundaries. Both in Power BI Desktop and the service.
- Using a full notation (e.g. "province, country") makes things worse - none of voivodeships is displayed on Filled Map and Map visuals. I don't get it - if Filled Map and Map are based on Bing Maps, then I would expect the interpreation of location data in those visuals will be the same as I get in maps.bing.com portal. But it's not somehow... Not to mention that for states/provinces/voivodeships it's more natural to use boundary map than bubbles to visualize data.
A repro .pbix file can be downloaded here: http://blog.sqlgeek.pl/Download/Voiviodeships in Poland.pbix. And you can see the report here.
Any thoughts and ideas would be appreciated. And yes, I know there are workarounds with Shape Map, R and Synoptic Panel, but none of them is good for business users.
So I've been trying to sign up for about 3 weeks now, and I keep getting the same error message "Sorry, that didn't work. There's a problem on our end. We're working on it, so try again later."
This problem has been persistant for 3 weeks and I'd like to sign up so I can buy PRO and continue.
I signed up, got the verification code, put it into the field and continued. |