Table.Distinct performance question

richard-powerbi · ‎06-14-2020

So there's the function:

Table.Distinct(table as table, optional equationCriteria as any) as table

If i do not fill in the optional equationCriteria, I notice that when refreshing the query, the number of rows in the little refresh window goes up to the full amount of rows of the table.

If I do fill in the optional equationCriteria and specify a column, the number of rows is equal to the number of distinct values in that column.

Is there is performance difference? Does it actually load more rows for a short moment in time when not specifying the optional equationCriteria?

v-eachen-msft · ‎06-15-2020

Hi @richard-powerbi ,

Do you get the same table after these two tests?

If equationCriteria is not specified, all columns will be tested.

Community Support Team _ Eads
If this post helps, then please consider Accept it as the solution to help the other members find it.

richard-powerbi · ‎06-16-2020

@v-eachen-msft yes the same table is returned. I understand that all columns will be tested, but I don't understand the difference in rows being (temporarily?) loaded? After the refresh finishes only the distinct rows are loaded though.... Maybe it's just a bug in the loading windows? Or is there something going on?