New Idea

'Tis a small thing, but I noticed that since today (approximately)...when looking at the list of datasets, in a workspace in the Power BI Service...when a dataset is in the process of refreshing, I no longer see a "circular arrow" icon to indicate that the dataset is currently refreshing.

 

It seems to be gone from all workspaces...for all datasets...whether it is a scheduled refresh or a manual refresh.

 

I really liked that icon! Can we please get it back?

 

For example, I took the following screenshot when my dataset had a refresh in progress...

 

Untitled.png

 

 

 

Status: Investigating

Power BI Desktop crashes when opening a report using a Power BI Dataset, when signed in with an account different from the one with access to the dataset. Expected behaviour would be e.g. a request for renewed credentials.

 

Steps to reproduce:

1. Open Power BI Desktop and log in with account A

2. Create report using a Power BI Dataset

3. Save and close

4. Switch to account B

5. Try to open saved report file

 

Result: "Something went wrong": "Sequence contains no matching element"

Details: See below

 

 

Feedback Type:
Frown (Error)

Timestamp:
2018-06-27T08:13:19.2743402Z

Local Time:
2018-06-27T10:13:19.2743402+02:00

Session ID:
e17c2a5f-1c0e-498c-aadc-2ea273f8ce3a

Release:
June 2018

Product Version:
2.59.5135.601 (PBIDesktop) (x64)

Stack Trace:
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at System.Windows.Forms.WindowsFormsSynchronizationContext.Send(SendOrPostCallback d, Object state)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.AllowModalDialogs(Action action)
at Microsoft.PowerBI.Client.Windows.LiveConnectHelpers.LiveConnectionPropertiesValidator.TryGetValidLiveConnectionProperties(IPowerBIWindowService windowService, ILiveConnectionProperties connectionProperties, ILiveConnectionProperties& validLiveConnectionProperties, Boolean& resultIsSameConnection)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.EnsureValidLiveConnectionProperties(Report report, IPowerBIWindowService windowService)
at Microsoft.PowerBI.Client.Windows.ReportPreparer.Prepare(Report report, PackageValidationResult mashupResult, IPowerBIWindowService windowService, Nullable`1 entryPoint)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIPackagingService.Open(FileStream fileStream, IPowerBIWindowService windowService, Nullable`1 entryPoint, PowerBIPackageOpenOptions options, Boolean& allCredentialsSatisfied)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.<LoadFromPbix>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.<>c__DisplayClassa`1.<<BlockUIAndRun>b__9>d__c.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion(Task task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod)
at Microsoft.PowerBI.Client.Windows.Services.FileManager.OpenFile(IPowerBIWindowService windowService, IPbixFile fileToOpen, Nullable`1 entryPoint)
at Microsoft.PowerBI.Client.Program.TryOpenOrCreateReport(IUIHost uiHost, ISplashScreen splashScreen, IFileManager fileManager, IFileHistoryManager fileHistoryManager, String filePath, FileType fileType)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClassb.<Main>b__0()
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass7.<HandleExceptionsWithNestedTasks>b__6()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

OS Version:
Microsoft Windows NT 10.0.17134.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 461808]

Peak Virtual Memory:
37.4 GB

Private Memory:
151 MB

Peak Working Set:
220 MB

IE Version:
11.112.17134.0

User ID:
e5b81239-eb6e-4a73-8843-2e63df754198

Telemetry Enabled:
True

DPI Scale:
250%

Supported Services:
Power BI

Status: Investigating
Hi ,
 
I have been facing issues while tyring to downloand .pbix report from Power BI service since yesterday. Is it a known issue? can some body suggest how to fix this?
 
Can't export to Power BI Desktop format
We couldn't export to .pbix format.
Please try again later or contact support. If you contact support, please provide these details.
Activity IDfc157f2e-5809-4c08-ab9a-096b6b0459ee
Request IDdd00a620-b403-fb92-5e64-0f07db2f6994
Correlation ID34cb47ec-a379-9cc9-24b2-baa5996edfd2
Status code500
TimeWed Jul 04 2018 15:01:13 GMT+0530 (India Standard Time)
Version13.0.5851.168
 
Status: Investigating

We have a production implementation of Power BI for which we turned on device based Conditional Access (CA), and added relevant AD groups. After turning on CA, users in the device based AD group are unable to sign in from Power BI desktop and also cannot sign in upon installation of a new Enterprise Gateway.

We get the following message: Unable to sign in. Sorry we encountered an error while trying to sign you in. Details: AADSTS50000. Device platform Unknown used by the user is an unsupported device platform. Supported device platforms are iOS, Android, and Windows flavors.

We are on a Windows platform and tested from Windows 8 and Windows 7 machines, and encountered the same error on both. This issue applies to October 2016 and September 2016 versions of desktop. To prove that CA triggered this issue, we used a test user not in the device based AD group. The test user was able to sign in successfully.

This issue is critical as it prevents us from being able to publish directly from Power BI desktop and prevents users from installing a new Enterprise Gateway.

Please let me know if you need any additional information. If you need Trace ID, Correlation ID or Timestamp, I can provide it via email.

Status: Investigating

Unable to connect to Project Online

Status: Investigating
by andrear Frequent Visitor on ‎11-24-2016 10:36 AM

Previously I was able to connect to Project online using Power BI.  I am now unable to connect to the Project Online Data Set using PowerBI.

 

I used it for two sites and both are now unable to connect whereas one was able to connect previously

 

 

error powerbi.JPG

 

 

Status: Investigating
0 Kudos

Excel data connection refresh failing in PBI online service. Just started failing today, July 17th 2018. Same behavior and error messages as when it failed in May of 2018.  (reference ticket "Excel Workbook Refresh Fails in BI Service" dated May 15th, 2018.

 Current error:

Failed Connections:Query - q_FM_Prog_Risk_Chart1_2017
Cluster URI:WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activity ID:b88eba82-7bb1-407a-aedb-d074def75377
Request ID:d1131862-a7c3-9014-0d6b-2c0a11e82c5a
Time:2018-07-17 13:10:36Z
Status: Investigating
0 Kudos

 

New OData parser (Implementation="2.0") ignores the filter restrictions (for fields with whith space in it) given in $Metadata

 

The new OData feed implementation in PowerBI (and unfortunately Excel in production, after last update) doesn’t respect the Non-Filterable property information and sends all of the filters directly to the server.

It happens for fileds with "space" in the field name.

The old implementation works good.

 

Example:

I have a OData feed named "Test" and I want to filter it in PowerBI by the field "Auto Number".
The field is described by the odata feed server as NonFiltrable (in Metadata).

 

The M statement looks like this:

 

 

  1. The “old”-good working implementation looks like this:

“let

    S1 = OData.Feed("http:\\test.test.net",null,null),

    S2 = S1{[Name="test",Signature="table"]}[Data],

    S3 = Table.SelectRows(S2, each ([Auto Number] = "123"))

in

    S3”

 

The Statement sent to server is: http://test.test.net/tables/Test?$top=1000

and everything is ok….

 

 

 

  1. Now using the new “2.0” implementation:

“let

    S1 = OData.Feed("http:\\test.test.net",null,[Implementation="2.0"]),

    S2 = S1{[Name="test",Signature="table"]}[Data],

    S3 = Table.SelectRows(S2, each ([Auto Number] = "123"))

in

    S3”

 

The statement sent to server is: http://test.test.net/tables/Test?$filter=Auto Number eq '123'&$top=1000

And this is not good - property AutoNumber is described as "Non Filterable Property" but PowerBI sends the filter to the server.

 

Metadata in both cases looks like this:

<?xml version="1.0" encoding="utf-8"?>

<edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx">

…….

  <Schema Namespace="Default" xmlns="http://docs.oasis-open.org/odata/ns/edm">

            <EntityContainer Name="Container">

                <EntitySet Name="Test" EntityType="TestNamespace.Test">

                    <Annotation Term="Org.OData.Capabilities.V1.FilterRestrictions">

                        <Record>

                            <PropertyValue Property="Filterable" Bool="true" />

                            <PropertyValue Property="RequiresFilter" Bool="true" />

                            <PropertyValue Property="RequiredProperties"><Collection /></PropertyValue>

                            <PropertyValue Property="NonFilterableProperties">

                                <Collection>

                                    <PropertyPath>Auto Number</PropertyPath>

……..

 

As You see the property “Auto Number” is described as a Non-Filterable property and it shouldn’t be sent to the server

 

 

Status: Investigating
0 Kudos

Hi All,

We are having issues with Time calculations when connecting Power BI to SSAS Multidimensional Cube in Direct Query mode.

To reproduce issue we created it on standalone machine with SQL Server 2017 Developer, latest Power BI desktop and AdventureWorks SSAS projects as example, so anyone can reproduce it.

We created simple calculated measure with pretty generic MDX to get Year Ago values based on Date Calendar hierarchy:

Internet Sales Amount YAGO =Aggregate(ParallelPeriod([Date].[Calendar].[Calendar Year] , 1,[Date].[Calendar].CurrentMember),[Internet Sales Amount]).

We then created a simple Power BI report with Matrix table:

  • Filtered to Year 2013 only (year used is from Date Calendar hierarchy).
  • Matrix with Rows added in specific order: Product Category, Product Line, Month Name (from [Date].[Calendar] hierarchy) and Sales Channel 
  • We used calculated measure Internet Sales Amount YAGO for values.
  • We enabled sub-totals on each level.
  • We expanded matrix to all levels.

You can see on screen below that sub-totals for any attribute that is before Month is not showing values:PBI_Totals_Issue.PNG

Now the same configuration in Excel works perfectly.Excel_Totals_Issue.PNG

We know that Power BI generates DAX per Total presented on screen. 

We captured that DAX generated via Power BI per level for subtotals and for some reason it is returning NULLs for those sub-totals.

We observed this behaviour with all variations of hierarchy navigation MDX functions (ParallelPeriod, PeriodsToDate, MTD, YTD, LAG(x), LEAD(x) etc.).

 

Questions:

  • Is this a bug?
  • If it is not a bug - what is the solution/workaround (please show example based on Adventure Works) to get same results?
  • Why it is fine in Excel and not in Power BI?

This affects basic MDX hierarchy navigation functions when displaying sub totals.

 

 

Status: Investigating
0 Kudos

Version:

Version 2.59.5135.421 64-bit (June, 2018)

 

Steps to reproduce:

  1. Set the date format of a column to *3/14/2001 (M/d/yyyy).
  2. Put this date into a table.
  3. Save the .pbix file and exit Power BI desktop.
  4. Change the locale and restart Power BI desktop.  At this point, the date format in the table changed.
  5. Exit Power BI and change the locale again.
  6. Restart Power BI Desktop

Results:

  • The date format no longer changes to the current local.  Repeating steps 5 and 6 have no effect.

 

Expected Results:

  • Every time I change locale and restart Power BI, the format of the dates should change.
Status: Investigating
0 Kudos

I'm trying to figure out why the Power BI service degrades to a point where it is unusable or crashes. We've had a Microsoft engineer on to have a look and advise us that our Smoothwall web filter is causing a Mixed Content error, which we're currently trying to resolve. However, I also noticed that the console in Google Chrome is indicating an issue with 'https://wabi-north-europe-redirect.analysis.windows.net/powerbi/refresh/subscribe' stalling every time. We just use the Power BI Service directly; no embedding or anything. Is this something to be concerned about?

Status: Investigating
0 Kudos

Hi

 

I have an aumoated refresh which works successfully each time, but the e-mail that get sent from the subscription shows that there is an error - but when I logon to look, everything seems absolutley fine...   

 

Where do I go from here?

 

2018-05-25_19h11_46.png

Status: Investigating
0 Kudos

I'm having an issue where I am connecting to an on-prem SharePoint list, and get an error about being unable to parse data. This strange thing is I'm using several other lists from the same farm with not issues. 

 

What would cause this, and how can I troubleshoot it? 

 

Capture.PNG

Status: Investigating
0 Kudos

Hi,

According to this page : https://powerbi.microsoft.com/en-us/documentation/powerbi-service-export-data/ 
The maximum number of rows that can be exported to .xlsx is 150,000.

When we try to export the data gets truncated after ~30000th row.

We are using free version.

Regards,
Jakub

Status: Investigating
0 Kudos

Normally, hovering the mouse over a visualization icon (e.g. "Pie chart" or "Scatter chart") will display a tooltip describing the icon/visualization.  However, on a 4k display, if the Power BI window is maximized, this tooltip will not display. 

 

The problem seems to present when the icons are positioned in the right-quarter of the 4k display, such as when the window is maximized.  If it is not maximized, and the window is positioned on the left three-quarters of the display, then the tooltips will display again.

 

The tooltips always work when the app is shown on my lower resolution monitor.

Status: Investigating
0 Kudos

See bottom of page: https://app.powerbi.com/visuals/info#submit

Link reads: Learn more about creating and submitting visuals

Current URL of link: http://go.microsoft.com/fwlink/?LinkID=671709

 

Instead navigates to page: https://powerbi.microsoft.com/en-us/support/

 

If this is intended, it's not clear that I will find help here for creating and submitting custom visuals. I expect to be taken to a page specifically about the topic. Changing the link to read: "Find support for creating and submitting visuals" might make this link a little more acceptable.

Status: Investigating
0 Kudos

Back in September there were some service issues that resulted in an 11 page forum thread here detailing everyones problems.  It appears those same problems are back.  Yesterday during a conference call everyone received the same errors of endlessly spinning loading circles and all the elements being replaced with a "See Details" dialog box.  Same errors we experienced back in September.  Screenshot attached, just an FYI.

 

powerbi_error.jpg

 

 

 

Status: Investigating
Idea Statuses