Issues

Hi

I am not able to "Update App" in Power BI Service. Not able to publish today. See error message:

Something went wrong
Failed to publish app.
Please try again later or contact support. If you contact support, please provide these details.
Activity ID: 1dd2b208-cd27-47d7-937f-bca59472b561
Request ID: 96e927f9-83b1-a531-8afd-312ca253738e
Correlation ID: 1f7d04a7-3eea-ebff-6a66-116bc2acb3e0
Time: Tue Feb 12 2019 16:11:47 GMT+0100 (Central European Standard Time)
Version: 13.0.8309.200

Please advice.

Thanks

Rgds

Henrik

In Power BI service, on the new filter experience pane :

The text of the filtering fields is not visible.

Keep up the good work though

Rémi

The latest Feb release of Power BI Desktop causes issues with existing diagrams in the new modelling view. 

1) Tables are auto-arranged where they were manually positioned before.

2) All relationship lines are missing but re-appear when you click anywhere on the diagram background.

3) When you move a table it does not always respond and you have to click on it again and move it, ususally the first table you trry to move on any diagram.

4) When you move a table the relationship lines do not move with the object and appear disconnected. You have to click on the background to get the lines to redraw to the new positions.

None of the above problems occured in the December build. 

Seems isolated currently but when connecting to a shared report, users are getting the following error:

Cannot load model
[Button] 
Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
Please try again later or contact support. If you contact support, please provide these details.
Activity IDac6d1e32-2f86-4359-b819-b028f378a76a
Request IDa529a945-125a-aec6-de52-95c413d5c31e
Correlation ID3f821d7c-64df-f49e-468e-022922d1a269
TimeMon Feb 11 2019 08:51:26 GMT-0500 (Eastern Standard Time)
Version13.0.8309.200
Cluster URIhttps://wabi-us-north-central-redirect.analysis.windows.net

Pre-emptively posting because it became a widespread issue back in December.  User has permission to the workspace, and was shared the report. This report is not in an App. 

Hello everyone,

I've been facing the same problem that other in the thread referenced below with the October and November (current) version of PBI Desktop. Currently my setup uses the x64 version over Window 10. It's quite annoying that no answer can be obtained in order to solve this.

The error pratically blocks the usage of internal context windows (such as file recover, save, add sources, etc...) and also crashes query editor leading to possible data loss due to force close required.

The error is intermittent and annoying, requiring to close Power BI without guarantee of results. It occurs on most popup windows in the application and also crashes the opening of Power BI Query Editor (application hangs with 30~processor usage and no response from UI).

Some small tricks works sometimes to help getting the bug to disappear, like retrying or alt+tab. But usually it is solved only for that occasion and by the next click the bug reappears.

I've also tried wiping out application cache without success.

This issue is also referenced in the thread: https://community.powerbi.com/t5/Desktop/Bug-in-PowerBi-Screen-dislocation/m-p/354864#M159782

Another example Get Data window:

Hello, 

I have been using Power BI Desktop and the Service for the last 3 years everyday and over the past week I have noticed that the Power BI Service is much slower than it has ever been. It can take 5-10 seconds per click in our environment in West US and in our customer environment. 

I noticed the most lag when I enter edit mode and try to change up reports. When I try to drag a new field on to the canvas from the data fields pane, you use to be able to see the field name next to the mouse cursor as you dragged around the canvas however now it seems glitchy and can take up to 5 seconds to appear. 

We did a webinar last week and have all of this abnormal latency recorded. We do not use Power BI Premium. 

Has anyone else seen anything similar? Please help us get back to user experience that we are used to!

Thanks, 

David

Colour scale conditional formatting on bar charts and tree maps works fine with the new experience in RS January 2019 Desktop application however the visuals are not rendering upon upload to the Report Server itself. 

Just an empty chart with the little spinning circle in the corner...

Also, any current reports that were using visuals with a measure in the "colour saturation" bucket have lost all conditional formatting therefore will need to be re-designed, not very helpful for business.

For some reason some of my reports (published about 1,5-2 weeks ago) has suddenly a change in background color on the report canvas from the background color I have set in the PBIX to a dark grey + the background surrounding the report canvas has also gotten this dark grey color. It has also happened to some of the visualizations bakgrounds for one of the published  reports. 

I have not made any changes to the PBIX or in the service since publishing these files, so this seems to be a bug. 

Background has changed for background surrounding canvas and for two viz on the report page

Grey report canvas in PBI service

Here is the image

https://www.dropbox.com/s/rygkrkukzisvvj4/Screenshot%202019-01-17%2015.10.03.png?dl=0

After updating Desktop to Nov 2018, my existing reports with Azure Data Lake Storage connections now fail to refresh, nor can I create a new connection to my Azure Data Lake Storage account.  I have just reinstalled Oct 2018 and everything works fine.

After entering the URL and then my organization credentials, I receive a message saying something like "Specify How to Connect" but with no button or action available to do anything about it.  I can either close or hit "Connect" again, and re-enter an endless loop of this warning message popping up.

There is an issue with the relative date slicer in Power BI service - one cannot select different options.

For instance, if you start creating a new report in the service and create a relative date slicer visual, you cannot change its default settings.

Or if you have a report developed in Power BI Desktop with a relative date slicer in it, when published to the service, you cannot select a different option for the slicer.

Has anyone else notice PowerBI Pro is extremely slow over the last week 12/10/18 to present day?  We have been getting the following messages off and on.  Reports sometimes run okay and other times they fail and it seem to be the reliability (lack) of the MS service.  If we run via the PowerBI Pro Desktop things run much faster and don't fail.  Over a month ago, we didn't have the issue, but it's getting worse as the days/weeks go by to the point it's unusable.  So far MS support does not seem to do anything and claim 

"We regret to agree to your concern. However, we try our best to provide our best to our users.

We apologize for the inconvenience caused due to the product limitation or product not working as per your expectation. I totally agree with you and all of your concerns and they are completely valid.

Our Product team pushes improvements and features on weekly basis. These improvements are planned well in advance. But there are some of the improvements which will have lot of dependencies due to which it takes long time and sometimes it becomes extremely hard for us to define an ETA even though we have a road map of improving the feature. We hope you understand the complexity here. Our focus is always on improving customer experience and giving what customer is looking for sooner or later."

This visual has exceeded the available resources. Try filtering to decrease the amount of data displayed.
Please try again later or contact support. If you contact support, please provide these details.

For the last 30 minutes it has not been possible to show reports in the service. They are just loading and never finishes. I have tried with reports from different sources, so the problem is in the Power BI Service. 

Can someone fix this ASAP? I'm based in northern europe.

It is currently not possible for me to refresh reports on the report service.

The error i'm getting is: The command has been canceled.. The exception was raised by the IDbCommand interface.

few info:

* This started on Saturday 1st december 2018
* Refresh works fine on desktop app

* It only affects report with incremental refresh ON
* I tried to rename the report and reupload but same error occurs
* When I disable the incremental refresh, report service works fine (but unacceptable for production)

Can you help. This is affecting the reports I have in prodcution and it is pretty urgent for me to fix.

We track dashboard usage metrics for accountability in our organization.  We've noticed that some viewers' activity is not being tracked in the usage metrics report.  Their views do not show up in usage metrics for the dashboard view or report view of our presentation.  They have definitely viewed the dashboard -- we've watched them share their screen while looking at it.

I have not an insane amount of fields, maybe 300 or so, and the search box freezes for like 20 seconds when I put in just a single common letter like s or e. seems like this should be really fast for 300 fields?

IE and Edge seems to crash when viewing a report witch specific type of chart. Problem occurs at least in this configuration: Windows 10 ver. 1703 64bit, IE 11.1088.15063.0, Edge  40.15063.674.0, Power BI Desktop 2.59.5135.421 64-bit

Steps to reproduce:
1. Create a new Power BI report with Power BI Desktop.
2. Get data from somewhere or enter data manually (you should have at least 2 columns, a category-field and a number-field, a few rows is enough). Data itself doesn't seem to matter (where it comes from, etc) in order to reproduce the problem.
3. Add Line and Clustered Column Chart to the report
4. Add the Category-field as shared axis and the number-field as the line
5. Make sure the settings for the line are as follows: https://imgur.com/a/pBTbSMY

(Format -> Shapes -> Stroke Width:4, Join Type:Bevel, Line Style: Solid, Show markers: On, Marker style: circle, Marker size: 6)

7. The graph should look something like this: https://imgur.com/mhK77j8
6. Save the file and publish it to PowerBI.com
7. Open up Internet Explorer or Edge and browse to PowerBI.com
8. Login and view the published report

What happens:
The browser starts to load the report but after a few seconds it crashes to an unknown cause

What should happen:
The report should load normally to be viewable and clickable

I think the problem is related to the markers on the line graph. The line seems to be missing the markers when the browser crashes. After a few crashes, the browser somehow is able to load the report and everything is working fine. If I clear the cache of the browser and restart it, the problem comes back.

Is the relationships display in Desktop supposed to save the current position.  In other words, if I drag the hierarchy the way that I want, isn't it supposed to save it?  I seem to get constant issues where I clean up the display only to come back in and it is all hosed up.  Sometimes it seems to save it properly.  What am I missing? I had the one below all nicely laid out and then come back in later and it is all messed up per below.

Hi guys,

We have an easy-to-reproduce issue that is critical to all users who have the Salesforce Objects connector in any of their queries.

The August 2018 version of Power BI Desktop (2.61.5192.601) does not allow the framework to refresh any queries that use the Salesforce Objects connector. [The Salesforce Reports connector is unaffected.]

To demonstrate this, simply add the following text into Power Query using the Advanced Editor.

let
    Source = Salesforce.Data(),
    SFDCObject = Source{[Name="Campaign"]}[Data], // Change this table name to be any SFDC table with >2000 records in it
    Custom1 = Table.Range(SFDCObject, 2001, 1)
in
    Custom1

The code is trying to return the 2001st record from any Salesforce Objects data set (assuming that it initially has >2000 rows!). Symptoms: The framework can happily extract the first 2000 rows without issue, but any subsequent rows fail to return and the Refresh data screen never completes. The only option is to cancel the dialog, and that often results in a hang.

As a result, we cannot refresh any Salesforce Object datasets within Power BI Desktop (Aug 2018 version). The functionality works fine with ALL previous versions of Power BI Desktop.

This is preventing us from being able to use the latest version of the software. please can you address this ASAP?

Many thanks,

Geoff Richardson