Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
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?
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 77 | |
| 37 | |
| 31 | |
| 29 | |
| 26 |