Reference guaranteed same order ?

[LeboeufHarry]

Hello,

We have a Table fetching records from a Azure Synaps Database, the table has a added index in PowerQuery.

We need to CROSSJOIN in DAX the table, but as the table contains over 25 columns we would create a 2nd table that reference this one and then drop all columns that are not needed.

But when I use a reference i've noticed that the data is fetched twice from the Source (at least that's what fething the records shows).

Problem is that with a parralel server you have no guarantee that the records will be in the same order, so it might be that certain records have a different Index in the big table than in the reduced table.

Is this thought correct or does the 2nd table only starts when Table1 is build and starts on the PowerQuery data to continue ?

[edhans · Accepted solution]

Not 100% sure of your question, but Power Query works bottom up, not top down. So if you have Query 1 that is referenced by Query 2 and 3, and 3 is referenced by 4 and 4 and 2 are loaded, PQ will start processing 2 and 4 and work backwards independently back to 1.

You can attempt to force the order not to change by wrapping the last statement in Query 1 with Table.Buffer() in my example. It will break any query folding