Number of Columns discrepancy

[mark-endicott]

Describe the problem

Before I run the analysis, there is a discrepancy in the number of Columns shown in the DAX Studio (482) and DAX Optimizer (401).

and

I am showing the results of the same VPAX file in both screenshots, but have obscured the file name & model name for data protection.

Happy to provide the VPAX file securely.

Power BI

Power BI Service VPAX file

Steps to reproduce the behavior

No response

Additional context

No response

Screenshots

No response

Anything else ?

No response

[albertospelta]

Happy to provide the VPAX file securely.

Hi @mark-endicott, you can send it to support@tabulartools.com

[albertospelta]

@mark-endicott thank you for providing us with the VPAX file.

The discrepancy between the two values is due to a different approach used in counting/displaying the number of columns. Specifically, the count shown by DaxStudio includes all columns of type RowNumber, while DaxOptimizer does not. The RowNumber columns are internal system columns automatically added by the SSAS server to each table, one per table, which identify the physical location of a row in the table and are not accessible in DAX.

In a future update we may consider changing this behavior to display a consistent value between DaxOptimizer and DaxStudio but, I can confirm that this difference has no impact on the result of the DaxOptimizer analysis.

[mark-endicott]

Thank you for the explanation, Alberto that makes perfect sense to me. I thought it would be something trivial like this and was not concerned.

I was flagging in case there was something for you to consider when DAX Optimizer is released to the masses.

Thanks, Mark Endicott (He/Him)

[albertospelta]

I am closing this issue as the change will be released in the next version of DaxStudio.