Last week our team start notice wired behavior of date filter.
we mainly work with the 'advanced filtering' for dates filtering to analyze data on an hourly level. when trying to pick the first date range it won't select the date that was picked in the calendar pop-up, but when selecting the second date range it's updating the first date range.
We tried using Chrome, Firefox and Edge - they all have the same behavior.
it's for any selected date, not to a specific range.
please click on the next link to see the issue record as GIF
When loading the app.powerbi.com page we are getting 500 errors for multiple http calls
Below you can find the console log from chrome debugger0
(index):163 GET https://wabi-north-europe-redirect.analysis.windows.net/powerbi/metadata/app 500 (Internal Server Error)
doInitialMetadataLoad @ (index):163
(anonymous) @ (index):163
web.bundle.min.js:26 GET https://wabi-north-europe-redirect.analysis.windows.net/metadata/notifications/summary?take=100 500 (Internal Server Error)
I have done a routine check of the datasets within our Premium EM1 Capacity and found a small number of reports (within the same App Workspace), have not been refreshed, some have.
The error is:
Processing error: You have reached the maximum allowable memory allocation for your tier. Consider upgrading to a tier with more available Memory.
This is a little striking, has anybody else seen this issue? We have an extremely small number of reports utilising EM1 Premium, with average to little usage (development phase), yet we have exceeded 80% memory thrashing 8 times in the last 7 days.
Are the particular reports failing at fault here, or have their refreshes arbitrarily been chosen to pause?
Since the latest PBI service update the Chiclet visual is not working within published reports. The issue has been raised in the Community forum but yet to be resolved:
From initial testig this is what we have found:
- various versions of the visual work within PBI Desktop (also variety of versions) but whenever published doesn't work as it should
- when published online the visual doesn't refresh the other affected visuals (instead it either does nothing, displays the wrong information, or requires a different visual to be clicked before it is refreshed)
- only under one circumstance were we able to get it published correctly (that was to an account we created years ago in O365 - all other accounts, including new accounts created in O365 today, fail to load the visual properly)
- the visual works fine within the Windows 10 PBI App
- the issue (that we have kown about) has been ongoing for the past few days - corresponding with the latets PBI Service update
Any help would be much appreciated as we have over 50+ reports using this visual and it's quite an embarassing to have to explain to users/customers we're not sure why or when the issue can be fixed.
My visuals are not displaying the negative values all the visualisations. I assume it is because the y axis does not want to show negative values. I cant find any options in the format editter which help with this problem.
The values chosen are simply input into a column of a new table that is not connected to any other tables and therefore there is no model to consider. The date column is only used to display the data in the visualisation.
So, this is logged over in ideas.powerbi.com. However, It's really a bug that can cause problems with report integrity and trust of users for reporting. Table visualizations cannot display duplicate rows. This is with summarization turned off for every field on the table, which is a separate pitfall. In SQL terms, the table visualization acts like a UNION, but it should act as a UNION ALL.
The workaround for the present is to do as advised in the forums, which is to add a unique column to the table visualization and then shrink the column width in order to hide it. In one case recently, however, I had to add an index to my query and then hide that column (with word wrap on, this hack also had the effect of resizing my rows to accommodate the wrapped but hidden index field). My users would like to see, for example, that a check detail has two line items for exactly $51. And I would prefer not to have to build workarounds.
I have the following Power BI Report
If you nativate to page 7, there is a column chart down the bottom. The column on the axis is formatted as TIME. When there is a single value selected for DATE in the slicer, the time formats correctly. When there is no date applied to the date slicer, the axis incorrectly formats as Date/Time.
We faced with issue that in our custom application with embedded report "Line and Stacked Column Chart" in see data mode has wrong view (names of columns in header are duplicated):
It was working fine in application before and also it is working fine right now in PBI Desktop (October 2017 Version):
Thank you in advance
When working with a Tabular AAS live connection in PBI, I've noticed that the organization of the fields is automated based on the presence of attributes in a fact/dim (if there are no attributes and only measures, PBI will designate the table as a Fact).
However, if a Fact table has a single attribute present, it will automatically label it as a Dimension, and I cannot override this command. There should be a way to toggle whether or not a table is a Dimension or a Fact, or have a similar folder structure like Excel, where measures are at the top of the field, and attributes are in a separate folder.
I created 5 new dashboards in Power BI Pro and shared them with individual users, most of which had never used Power BI before.
When these users navigate to the report, but they received an error, "Dashboard Security Check - It looks like you don't have access to this dashboard. You can request access from the owner." So somewhere between signing up for a Pro License and arriving at the /dashboard/ page, their access privileges get lost.
If they Request Access, and I approve it through the Share Dashboard feature, I will receive their request, but it comes as a separate user (email address not shown, just the person's first and last name) and the email address that was used to send the invite is shown as unopened (cancel invitation link is visible) even though they are using the same email address to request access.
I fear that this is a security risk, if I approved a request to see a dashboard because I see a familiar name, how do I know that this request is coming from within my organization if I cannot see their email address?
Can you test this process a bit and see if there may be a bug in the system? I am unable to send a screenshot because I already approved all the users!
We are running into the problem that our redshift cluster, that is not open to all IP addresses, can't be reached from PowerBI Service as it is using multiple IP addresses that are also changing on weekly basis. But it can't be the idea of having this Redshift cluster open to all connections. For a company like us this is absolutly not acceptable. Is there any solution for this issue.
PS: connection on or Redshift Staging Cluster where we allow all connection works perfectly fine...
After September 2017 update (2.50.4859.502) we've faced an issue similar to one some users had reported in February: when we try to get data from Analisys Services, where our MS Dynamics OLAP Cube is located, we end up with the following error: 'Unexpected error: Object reference not set to an instance of an object'. Rolling back to previous PBI Desktop version resolves the issue.
I was hoping this bug would be fixed in October update, but that didn't happen...
I have been trying to roll out Power BI to my organisation (it is a rather large organisation with many users all over the country) whilst our Central IT department is working through upgrading us to Power BI Premium and I have discovered a bug that the Microsoft Customer Service person who is helping me claims is by design.
Bug that was discovered: When I share a report via a dashboard to a new Power BI user (doesn't already have a Pro Licenses) and the user signs up for a Pro Trial to see my report, I need to cancel the invite and resend it.
Steps to reproduce:
- Create a report and publish it to a group
- Create a dashboard for the report and share it with a user who is not a Pro user yet
- Have your user sign up for the Power BI Pro Trial
- User will get "Sorry, we couldn't find that report" error
- After your user signs up for a Power BI Pro Trial (step 3 in the above), go to your dashboard and click "Cancel Invite"
- Resend the invite to your user
This works, however, it is a bug and it is creating a lot of extra work for the people who are producing / sharing reports as well as frustrations from our end users.
If you could fix this or assure that this will be fixed when we move to Premium, that would be really helpful in getting our users to adapt to Power BI as their new reporting tool.
I am listing some bugs / issues I have found with Power Point files that are generated by Power BI. Please let me know if I need to provide more detail, thanks! Otherwise very happy with PBI, it just needs some fine tuning.
On Power BI Export to PowerPoint...
- Text boxes lose text alignment and background color (font-family and sizing are OK)
- Text boxes, shapes, and cards all "superimpose" themselves (with styles applied) onto each other if they overlap
- Even elements that are 'lower" / "behind" other objects in terms of arrangement, still superimpose on other objects
- This is probably by design to fuse together nearby objects but it's not figuring out layering priority correctly
- KPI type visuals lose font format and sizing (they do keep styles like color and background color)
- Note: you can't change or control font format / style for KPI visuals anyways
- All objects have hyperlinks to Power BI which is very busy, these open your web browser when you go into presentation mode which is annoying
- Background images only show up when there is a Power BI element layered above it, otherwise blank
- HACK: Add a full-sheet Power BI "square shape" that is 100% transparent, 0pt border but beware of superimposing issue and hyperlink issues above)
- PBI Reports cannot be exported to PowerBI with "interactivity" meaning if you update a slicer or filter in the web browser without saving (very common...), your export to PowerPoint will be the "original" version
- I realize this is documented as how PowerBI currently exports PPT from back in March 2017 but it should be fixed to at least give the user an option to export with modifications or original.
When combined with non-SQL-datasources query-folding will often not work: http://www.thebiccountant.com/2017/07/20/sql-query-folding-bug-still-alive-sucking-powerbi-powerquer...
This is really nasty. As performance optimizations is such a black art still unfortunately, many people will probably just throw the towel here, so I expect a high number of unreported cases here, so please fix.
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.
I recently had to re write some reports due to changes made to our data warehouse, initiall i made the changes and attempted to republish the data, however the file would not publish, and just kept spinning. I unistalled and reinstalled the gateway and powerbi and tried again, and this time recieved an error stating powerbi unable to write data to the transport connection.
I removed all data sets and reports from the web app, saved my pbix file in desktop using a different name, and tried publishing through desktop again, and recieved the following error: An Error occurred while attempting to publish 'sales information.pbix': Exception of type 'microsoft.powerbi.client.windows.services.powerbiwebexception' was thrown.
I then tried to import the pbix file from the web and recieved this error:
Please try again later or contact support. If you contact support, please provide these details.
i notice on the service status page there is an awareness flag stating:
We are experiencing a temporary issue where some users may not be able to update their Apps or Content packs. Engineers are aware of the issue and are working on a fix. Next Update by 09/08/2017 11:00 PST
Is this what is causing my problem, of is there another reason? If this is the issue, is there a work around?