New Idea

Trying to open my PBIX files and the desktop application. nothing open up. It just gets stuck. i have even downloaded the App again. below is the Pic of the error.


BI issue.PNG

Status: Accepted

Noticed yesterday that when testing "view as role" in the PBI service a selection seems to get de-selected immediately. However it works in the Desktop app. Still not working today so figured that this might be a bug in the online service? Anyone else with a similar issue?



Status: Accepted

The supplied URL must be a valid 'http:' or 'https:' URL ???

Status: Accepted
by Sean Super Contributor ‎03-12-2018 09:29 PM - edited ‎03-13-2018 07:45 AM

I have a PBIX file that updates every Monday from a web page.

Last Monday March 5th (before the March 2018 Update) all was fine Smiley Happy

Today Monday March 12th (after the March Update) I get this error Smiley Sad

The supplied URL must be a valid 'http:' or 'https:' URL

Well the URL is working and it opens fine in any browser! (Firefox, Edge, Chrome)

Here's the error I see in the Query Editor

URL Must be Valid.png

Oddly the URL still works in Power Query but not PBI

I've duplicated the issue with this different link

Here's result in PBI

URL Invalid PBI.gif


And result with same URL in Excel

URL Valid Excel.gif


Thanks! Smiley Happy

Any ideas / suggestions would be greatly appreciated!


Desktop Forum Link


UPDATE: This happens with both March 2018 Versions I've tried so far

2.56.5023.861 - March 7 and

2.56.5023.942 - March 12

Both don't work and say URL is Invalid!


Also I was able to downgrade to Feb 2018 and I do NOT encounter this issue there!



Status: Accepted

RLS test as role not working in service

Status: Accepted
by robby1982 New Member on ‎02-27-2018 11:31 AM



This used to work fine but when I try to  'test as role'  today in service, whatever emailadress I select it just doesn't stick. The apply button is also disabled. 


Anybody else having this issue? (no problem in desktop)


Kind regards,



Status: Accepted

As per the title all basic date slicers are stuck in the US date format and cannot be changed. My regional setting are set to UK and changing this around does not fix the issue.

Status: Accepted

Lately while I was maintaining the published reports from the Power BI desktop; noticed that after save, when I clicked on the Publish button, it calls the sqldmper.exe (the command window) and crashes; sometimes hanged and had to kill the task.

Then I noticed PBD keeps logging me out during publish, calls that sqldmper.exe and after crash, have to relogin and publish till now.

I believe there's a bug in latest update; I am running the january 2018 update.


Is anyone else facing the same issue?




Status: Accepted

There was a similar issue last year. It seems that has re-occured.


When I attempt to publish a report and have not signed  into the Desktop yet, a command prompt box appears then disappears and Power BI crashes. Also, it seems that   after the January 2018 update, Power BI requires to re-signin for each report created prior to installing the  update.  Normally after I have  already signed in, Power BI will not request for  another  signin the next time  I open the same report. 

Status: Accepted

Hi if I include a custom visual added from "My Organization" in the marketplace, when I share the report using "Publish to Web" then the custom visual doesn't appear.


In the browser console window I see the following errors:ptwbug.png









If I add the custom visual "from file" then it works fine.

Status: Accepted

In the March PBID (Version: 2.56.5023.861 64-bit (March 2018)) - If you delete a page in a report, it does not prompt you to Save when you close the pbix, and does not Save the changes either (assuming you do not explicitly Save the file first). When you reopen the pbix the page you deleted is still there.

Status: Accepted


After I updated my Power BI Desktop to February update I noticed that everytime I refresh the datasets the sorting by column resets and goes to default. That's so disturbing that I will have to downgrade to the December update, because the January upgrade had issues in DirectQuery mode.


I've tested on two different machines and on the machine with the December version there was no such issue as reseting the column sort to default.

Status: Accepted

DirectQuery Refresh Broken update january 2018

Status: Accepted
by Goofr Frequent Visitor on ‎01-09-2018 08:11 AM


Seems to me there's a bug in the new January update.
I have a report using DirectQuery, and when I refresh my model it keeps saying:
"Connecting to tables from more than one database isn't supported in DirectQuery mode.".
If I rollback my installation to PBI December, the refresh works, as I don't have multiple datasources in my model.

Thanks in advance.



Status: Accepted

I seem to be having issues with the recent Power BI update (December 2017), whereby when invlaid relationships are trying to be established between two tables Power BI exits with no warning.

Status: Accepted

Power BI Desktop Crash post Feb 18 update

Status: Accepted
by Stharwani Regular Visitor on ‎02-06-2018 05:30 PM

PBI Desktop is still crashing on prublishing a file.


The same error as previour month, opens up a SQLDumper.exe.


Please resolve

Status: Accepted

In Power BI Desktop Jan 2018 release, with a Date or Date/Time field selected in the Fields pane, when you navigate to the Modeling ribbon / Format / Date Time menu, the options at the top (marked with an *) that respect the machine locale now show in US format (e.g. M/d/yyyy) on machines with non-US locales e.g. English (Australia).


This appears to only be a problem in the display of the menu.  When date fields are shown in a visual e.g. a Table, the expected non-US locale is used e.g. d/M/yyyy.  


This issue was introduced with the Jan 2018 update to PBI Desktop.

Status: Accepted

Bug with slicer and Bookmark in Service

Status: Accepted
by rmccormick Visitor on ‎01-11-2018 02:27 PM

In the Power BI Service, I have uploaded a project that utilized a bookmark to reset several slicers on a page.  This works smoothly in Desktop, but in the service, it does not function reliably.  Is there a workaround for this, or is this a known issue?  


Using the standard drop down slicer and no custom visuals.  



Status: Accepted

Hello everyone, 


Since the new December version has been released, I keep having crashes of Power BI over and over trying to link two tables... 


As soon as I want to create the link (drag and dropping a dimiension to a table to another table) the windows terminal opens with SQLDUMPER.exe and close/crash Power BI.


I have never experienced this before the last release.


Thank you for your help

Status: Accepted

When I try to update a content pack, (in, cog -> View Content Pack ->  Edit (an existing content pack) -> click UPDATE button), I see an error message that begins "The following groups have failed validation..." This happens with all of my content packs, even when there are only 5 members of the workspace that the content pack is publishing to, and all members are definitely still current staff members. Any ideas?

Status: Accepted


Status: Accepted
by jak82 Member on ‎01-10-2018 12:27 AM

Okay,  We had the issue last month with unable to join tables together.


Now after updating to the January I cannot load any DIRECT QUERY pbi files as it says it cannot connect to multiple databases when it is only connecting to one.


We are a multi million pund business and have made an investment into using PowerBI as tool.  This breaking on and off all the time is not very viable.  Please can this be fixed ASAP!!!!!!!!

Status: Accepted

After the January 2018 update, the formatting option for date (dd/MM/yyyy)  disappeared.


Is this a bug?



Thanks in advance.






Status: Accepted

Select query in odata v4 is ignored

Status: Accepted
by agur Frequent Visitor on ‎01-31-2018 04:16 AM

When using $select in the query string for an OData v4 service it is ignored.

For example:

= OData.Feed("https://<org>$select=name,actualrevenue")

This returns all opportunities with ALL fields, not only name and actualrevenue


= OData.Feed("$select=id")

This returns ALL fields, not only group ID


This has a HUGE business impact, as this makes loading data in PBI reports extremely slow. The consensus in the Dynamics 365 environment is to export the data to an Azure database before loading it into PBI, which breaks security hierarchy and makes everything less user friendly.

Status: Accepted