Forum Discussion
Append table lost rows
dgbraqe, This issue should be now be fixed. Please download the Power BI Desktop July release and let us know if things are now working as expected.
Ehren
edhans, perfect your observation.
When we use the DAX function, the problem does not occur.
This shows even more that we have a problem with the M (Power Query) language, I understand that the use of "Table.combine" (M language) or "UNION" (DAX language) should have the same result.
I opened a ticket with Microsoft, I will inform you as soon as I have a definitive answer.
Anonymous, please, leave the topic open until we understand the reason for the difference between the M and DAX language.
Community ChampionThanks dgbraqe. Please keep us posted on this.
I am wondering now if my issue here is a result of APPEND weirdness in M Language, as the resultant table is from an APPEND in M. Except in my case, it works in PBI Desktop, but not in the service.
EhrenMicrosoft Employee
dgbraqe, I've tried reproducing this locally (using SQL data refreshed via a Gateway) and am unfortunately not seeing any duplication. Would it be possible for you to try the following?
- Try duplicating the query that does the Table.Combine operation, and then buffering the result (i.e. add a step at the end that does = Table.Buffer(previousStep)). Does this version of the query exhibit the same behavior?
- Try duplicating the query that does the Table.Combine operation, and buffering each individual table being combined (e.g. = Table.Combine({Table.Buffer(Query1), Table.Buffer(Query2)})). Does this version of the query exhibit the same behavior?
- Try duplicating the query that does the Table.Combine operation and doing a group by and count of the unique field you're seeing duplicated, then filter for Count > 0 (which should return an empty table when run locally in PBIDesktop). When refreshed via the gateway, does this query produce any results?
Also: what version of SQL Server are you pulling from?
Thanks for your help.
Ehren
Hello Ehren
I am using the SQL versions below:
Base 1 - Microsoft SQL Server 2014 (SP2)
Base 2 - Microsoft SQL Server 2016 (SP1)About the tests you requested, the Microsoft team had already done some testing using the "Buffer". Yesterday I had another meeting with the product team, they did some tests and collected the "trace" of the data load. I was told that you are prioritizing the subject.
I warn you as soon as they return.