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.
Our report - which is based on MY SQL Queries - seems to experience difficulties regarding the scheduled refresh. This is the error that we got back:
If anyone can offer any advice or provide further information that would be highly appreciated
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.
It looks like that filtering is not working properly when using three or more slicers/filters in Power BI Online Report view. It works on the desktop version but when publishing to Power BI Online some of the relations between filters is broken.
See video for reproducing the issue:
We are trying to import the JIRA issues on to Power BI using the JIRA content pack and generate the dashboards. But this is failing with an error message "We couldn't Import the data" . Additional error information that I can gather from the error detail is "We found extra characters at the end of JSON input.. The exception was raised by the IDataReader interface."
1. Provided the JIRA issues link - "https://jira.companyname.com.au/issues/?jql=project%20%3D%20XXX"
2. Authentication selected as Basic and provided validd JIRA user name and password
3, Then tried connecting but failed with the error message
JIRA instance - Cloud
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.)
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
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?
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.
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. |
Have a dashboard report that when filtered in edit report view and then saved does not save and the following message appears. Have another report in the workspace and this saves fine. Deleted the dataset and re-uploaded but this has had not effect.
We have created an iframe using "Publish to Web" feature and tried to embed it in SharePoint. This is working fine with chrome/edge browser, not in IE. This issue has started on last month ( May 2017).
I'm a long-term user of Power BI and would expect to be eligible for the Extended Pro Trial (I've received the notification e-mail about the extended trial). Today, when I try to share a Power BI dashboard I receive a message telling me that I must be a pro user to do that, the message invites me to 'Upgrade Now'. When I click 'Upgrade Now' I'm shown a page of options, and select the middle one to 'Share and Collaborate' which it says I can try for free - I'm guessing this is the extended pro trial. Selecting this option leads me to another message that this says I don't need to sign up for pro because I already have a licence. I'm then trapped in a cycle whereby I can't share my dashboard because I apparently don't have a pro licence but then when I try to upgrade it won't let me because it says I've got a pro licence already. Looking at my stoarage settings I've got 10 GB assigned which suggests pro but at the same time I'm described as a 'Basic User'. I'm completely confused and haven't been able to find anywhere I can contact Microsoft for help. Can anyone help me? Thanks
I have a requirement to emebed Power Bi report in a Html file hosted in SharePoint Online site. The content was displayed properly in all browsers initially.Suddenly we have observed issue in IE browser and it always dispalys blank.The other browsers work as expected,It would be great if any one helps to sort it out.
Image link: http://imgur.com/HqCky3f
I have pasted a link to the image above, I could not embed it for some reason.
I am pretty new to PowerBI, so be nice. I have loaded some geographical data against the UK using a postcode file on a map.
I get a yellow warning error bar at the bottom of the ESRI/ ARCGIS map that tells me: "Failed to Locate 23 Features".
I cannot work out how to interrogate, review or fix these 'features'.
It would be really helpful if error reporting was able to be scrutinised a lot more clearly for a novice like myself.
Any comments and support would be welcome.
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.
This error occurs more often than not when Updating my App from the App workspace.
Very Frustrating. Thanks.
We have currently a project, that should deliver several PBIX-Files to different customers.
Every PBIX-File should access the same SQL Azure Database, but should use different SQL Login-Credentials (since not every customer should be able to access all database objects). If we now wanna test this on our local environment, and create these PBIX-Files with different SQL Logins, it always overwrites the SQL Logins of the global Datasource. This is indeed annoying, but can be worked around by just entering the logins again and again before publishing.
The real problem shows up when we publish these PBIX-Files to Power BI Web and try a scheduled refresh of multiple datasets:
Since the SQL Login gets always overwritten as soon as you publish a new PBIX-File, it kind of uses a random SQL Login, so we cannot guarantee to provide the correct data to the original files.
Our question now is if it's really fully intended to always overwrite the logins of a global Datasource, even in different, shared workspaces or will there be any solution in the future to store the logins with the files or provide a section to manage the Datasources properly (maybe analog the SSRS-Datasources)?
I noticed today that ALL of my attribute slicers are now set to 'highlight' other visuals rather than 'filter' them. I didn't make this change. They have been set to filter for 2 months. Perhaps this was triggered by the January update? Lots of rework involved to set them up to filter again.