New Idea

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.

Bug: Table.ReplaceValue kills all column types

Status: Accepted
by ImkeF Super Contributor on ‎08-03-2017 11:01 AM

When used in combination with "each" in the second argument, Table.ReplaceValue kills all existing column types (sets them back to any). Please fix:

 

https://social.technet.microsoft.com/Forums/en-US/c3f118eb-acb2-4e36-a398-d6c3759e795f/tablereplacev...

Status: Accepted

Bug: Section1 results not loaded to data model

Status: Accepted
by ImkeF Super Contributor on ‎08-03-2017 10:54 AM

The result of: Record.ToTable(#sections[Section1]) are returned correctly in the query editor, but not loaded to the data model. There, only the value of the current query will be returned.

 

In Excel, this works fine, so both results are the same: A table with all queries in the current file.

Status: Accepted

When we run PowerBI Version: 2.46.4732.581 64-bit (May 2017) and connect to a SAP Hana 2.0 everything works fine and you can see the Calculation Views listed in the Navigator.

 

When we run the latest download July it can connect to a Hana 2.0 database but we do not see the list of Calculation views in the Navigator.

 

Both builds are fine for Hana 1.x databases.

Using Hana 2.0 64 bit ODBC driver.

Status: Accepted

We have an issue that our PBI file works fine but when row level security is turned on we get error messages. 

 

We have tracked it down to a caculate measure. When row level security is off this measure works fine  - 

 

CALCULATE (sum(UnitSalesValues[Sale Values]), 'UnitSalesValues'[Attribute]= "Sold prior to qtr" )

 

When row level security is turned on this measure creates the following error is the visual. If the bolded part is taken out the measure works fine. 

 

Colukn't load the data for the visal

An unexpected exception occured. 

 

This same file was working with last months version of PBI. The data in UnitSalesValues is visable with the row level security turned on and has values for "sold prior to qtr". 

 

However, even if we use last months pbix file it does not work in the PBI Embeded enviroment. 

 

This certainly seems to be an error in PBI. Further when the row level security is first turned on a black screen apears and the following program is run. 

 

c:\Program Files\Microsoft Power BI Desktop\bin\SQLDUMPER.EXE

 

 

Status: Accepted

Hi all,

 

I have a client who is on the latest release of Power Bi Desktop (v 2.46.4732.721), although this issue also occurs on the previous version (2.46.4732.581). When they create a new measure on top of a live tabular model connection and set the formatting, the formatting only persists for that Power BI Desktop session. When they save the file and close and reopen, the formatting reverts back to the default, which is especially unreadable for percentages and currency. Is this fixable? Thanks!

Status: Accepted

Yesterday, all my datasets were refreshing just fine but today nothing happens.

- The automatic refresh hasn't done anything.

- When I press "Refresh now", I get a "popup" saying "preparing refresh" for a split second and then nothing happens.

 

The only way to update the data is to refresh the Desktop version and then upload it. 

 

I have datasets connection to an on-premises database and one connecting to a sharepoint site.

- The on-premises connection usually works perfect, but now nothing happens.

- The sharepoint connection usually brings up an error,  if I try to refresh, but now nothing happens (I just tried it this time as a test, as it usually doesn't work automatically).

 

Can you please help troublefinding - It seems like an issue on you online portal somehow.

 

Thanks in advance.

 

// Tommy

Status: Delivered

Bug in "Don't include in Report Refresh"

Status: Delivered
by ImkeF Super Contributor on ‎01-10-2017 07:58 AM

There's a bug in "Don't include in report refresh" like described here: http://community.powerbi.com/t5/Desktop/Disabling-quot-Include-in-Report-Refresh-quot-works/m-p/1017...

unfortunately I didn't test correctly and this thread is closed, but the bug is still there and preventing solutions for problems like this:

http://community.powerbi.com/t5/Desktop/Big-file-needs-no-update/m-p/111341#U111341

 

If the query that shall not be refreshed is not referenced by any other query or part of a UNION-operation in DAX, then everything works fine, but if it is referenced as mentioned, then it will be loaded again.

A lot of the usecases for this features are of this kind, so this bugfix is really needed !!!

Status: Delivered

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.

 

MDX

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.

 

This works:

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].[1100], [0FISCYEAR].[K12016])

 

Doesn’t Work

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].[1100], [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.

 

Tableau

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.

 

Thoughts?

Hi, 

A few days ago i noticed that the colours of the highlighted filters become different afther being published. I've checked and the system is updated, including pbi desktop.

 

On the pbi desktop app this is how it looks a filter with the highlighted 2016:

1.PNG

After being published, the highlighted 2016 looks like this:

2.PNG

Somehow, all filters based on this visual in every dashboard have the same error, but the filter works. 

Thanks

Status: Delivered

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. |

Help?

 

Erico

 

Status: Needs Info

Hello everybody,

 

I dowloaded the last update of Power BI of this month today morning, and suddunley I found that the description shown with any DAX formula when creating a new calculated measure is written with a strange langage, let's say it is like a crypted langage.
It is joined a screenshot that shows the case.
Could anybody explain what is matter with Power BI.

 

cheers,

 Sans titre.png

Status: Accepted

Table.Profile() Bug

Status: Accepted
by Simon_Nuss Frequent Visitor on ‎06-09-2017 08:32 AM

There are two bugs that exist in Table.Profile() that can be replicated against the WorldWideImporterDW using the below instructions:

 

1) Executing the below query results in, "Expression.Error: The Duration operatnio failed beacuse the resulting duration falls outside the range of allowed values".

 

let
    Source = Sql.Database("SQL_Server_Name_Goes_Here", "WideWorldImportersDW"),
    Dimension_City = Source{[Schema="Dimension",Item="City"]}[Data],
    Profile = Table.Profile(Dimension_City)
in
    Profile

1083573.png

 

 

2) Table.Profile() will effective DDOS a data source when [CreateNavigationProperties = true].  The below script results in 1,619,884 queries (7 (columns) * 231,412 (rows)) being folded back to the data source.  It is worth noting that [CreateNavigationProperties = true] is the default in Power BI.

let
    Source = Sql.Database("SQL_Server_Name_Goes_Here", "WideWorldImportersDW", [CreateNavigationProperties=true]),
    Fact_Order = Source{[Schema="Fact",Item="Order"]}[Data],
    Profile = Table.Profile(Fact_Order)
in
    Profile

1083574.png

Status: Accepted

"Quick measures" is translated to two japanese.

 

In Option-Preivew dialog.

  "クイック メジャー"1.png

In other menu and dialog.

  "簡易分析".

1.png

 

 

 

 

 

I want to translate all "Quick measures" to "クイック メジャー".

 

Regards,

Yoshihiro Kawabata

 

 

 

Status: Accepted

We have a report that connects to a SSAS tabular model using Direct Query. In order to make some of our measure names more user friendly in a report, we created some Report Level Measures (the new feature in the May release of Power BI desktop) and formatted those new measures appropriately (whole number with commas, decimal numbers with commas and two digits after the decimal, percentages, etc.) but we lose that formatting after saving and re-opening the file. We also lose the formatting after publishing the report to the Power BI service on the web.

 

Has anyone else experienced this issue? Any known work arounds?

Status: Accepted

Global SQL Server Datasource Credentials

Status: Needs Info
by Jackinus Visitor on ‎05-18-2017 04:42 AM

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)?

 

Status: Needs Info

This has been an issue since the Original April Release.  I continue to revert to the March 10th release as it is the last release that allows me to refresh my data.

 

I just tried the latest May release and the issue persists...

 

I have received two similar error messages between my two data models:

 

First: "DataFormat.Error: You attempted to open a database that is already opened by user 'Admin' on machine 'xxxxxxx'.  Try again when the database is available."

 

Second: "DataFormat.Error:  The database has been placed in a state by user 'Admin' on machine 'xxxxxxx' that prevents it from being opened or locked."

 

I have found that the error only occurs when refreshing from a database that sits on our network drive - I am using an Access Database as the datasource and if I copy the database to my local machine and redirect the datasource in Power BI Desktop, then the model refreshes without issue.

 

Please fix this issue - having to copy the database locally on my machine in order to refresh is not a viable work around.  I continue to run the March 10th release until this is fixed, wishing that I could access some of the new features that were introduced in April and May...

Status: Accepted

I have published one report to my own workspace and to shared workspace. I get update schedule working in my own workspace but in shared workspace I cannot set up credentials because of the following error:

 

error.png

Is there anything that I'm doing incorrect or what is this sorcery?

Status: Needs Info

If you try to upload Power BI content and haven't checked to see if you are still signed in when you try to publish the file PBI hangs. You can't enter credentials as PBI is attempting to upload the file.

Status: Delivered

NIGHTMARE!

I am building a couple of dashboards in desktop, done 60Hrs this week alone.

Working fine yestereday- all use excel files and tables as data sources

Today- Update inside windows 10 insiderPro build 15002 this morning

Update to Jan 2017 PowerBI

Now every dash won't update with the message 

DataFormat.Error: The input couldn't be recognized as a valid Excel document.

Every file opens fine in excel not corrupted, even tried with new data, same message

 

I've rolled back to an earlier Power BI but get the same error, any other ideas welcome.

Is there a setting in the build 15002 that doesn't recognise excel files as excel files???

 

Status: Accepted
Idea Statuses