This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I have noticed some strange behaviour in Power Query when merging records.
If I have two tables which are sorted based on a date field and then merged, the sort is ignored at the Table.ExpandTableColumn stage of the query. I have noticed this as I had filtered to a single record on one side of the merge before conducting the merge and, once the merged query was expanded, the single record had been replaced by a record which had previously been filtered out.
The other scenario is where I have sorted the data based on a date field and then used Table.Distinct to remove duplicates (this is to only show the latest dated record). The sort order is ignored and a different record is selected - I would expect the first record to be retained.
Unfortunately, I cannot share the data as it is sensitive customer data.
I have found a way around the issues by adding either an index column or by using Table.Buffer. I was just wondering if there is a better solution for this or if this is indeed a bug with the software?
This could be a bug.
Could you please replicate the issue with dummy data and raise a support ticket?
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 36 | |
| 28 | |
| 28 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 68 | |
| 39 | |
| 33 | |
| 24 | |
| 23 |