Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
An issue came up when I merged information from another query into an existing query (JoinKind.LeftOuter or equivalent to a vlookup in Excel) where, upon expanding the merged query, rows were inexplicably deleted and merged information came up null, even though there was matching data. There was no indication that rows were deleted other than analyzing the resulting table and noticing that information was missing. I mitigated this issue by adding Buffer language, however, the step takes so long now that the query is basically useless. Data being deleted without reason is a serious issue, particularly because there is no indication that rows of information were removed. I am considering using an alternate tool because of this issue.
Hi Christina,
what I wanted to say is that there is currently no accepted bug from Microsoft about such behaviour.
So if in your case, data is really missing, then I would recommend to open a ticket for it.
Imke Feldmann (The BIccountant)
If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!
How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries
Hello Christina,
I read that thread as being about the sort order not being kept. Which - at the end was confirmed as exptected behaviour and not a bug.
So your case looks different to me. I am not aware of a confirmed bug that deletes data after merges.
Imke Feldmann (The BIccountant)
If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!
How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries
Hi Imke,
I'm afraid this still does not address the issue of data being deleted.
Regards,
Christina
Hello @CRamstedt ,
haven't heard of this problem before.
Please keep in mind that the order of the rows will not be kept after the column expansion. So when checking for matches, you must consider the whole row.
Imke Feldmann (The BIccountant)
If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!
How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries
Hi Imke,
Thank you for the response, however, I have considered the whole row, so this does not address the issue.
After doing a search, I found the following thread addressing this issue and was wondering if there is an update to the bug.
https://community.powerbi.com/t5/Desktop/Power-Query-Row-disappear-after-expand-column/td-p/643967
Kind regards,
Christina
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
10 | |
8 | |
6 | |
6 | |
6 |