Forum Discussion
Merged Values Change Before and After Query
- 1 year ago
Hi could you try first sorting those fact and dim tables based on the key columns before trying to merge those tables
Then use Table.Buffer to freeze the data afterb sorting
Then merge them
If there are transformations to the data try doing those before the merge happens
- 1 year ago
Hi Anonymous ,
The real question is: Why is it important that your rows stay in the same order? The Vertipaq engine will only muddle them up again as soon as you apply the query to the model.
Pete
- 1 year ago
And sort order is not define in PowerQuery, except after a sort. As was stated by Imke in the solution of the post you referred to in your post.
Sorry, I don't get it. What is you problem? The Merge of the employees show the correct keys as far as Ican tell. What were you expecting?
Does it have to do with the sort order? I would do this last (or not at all and leave it to PBI or Excel.