MAXX is weird against TOPN?

[scottsen]

If I execute this:

EVALUATE
TOPN (
COUNTA ( MyTable[MyValue] ) / 2,
ALL ( MyTable ),
MyTable[MyValue],
1
)

I see values come back as the lowest values in my table: 1,1,1,2,2,2. All is good.

And then wrap the same exact TOPN in a MAXX... inside a measure / calculated field...

=MAXX(
TOPN (
COUNTA ( MyTable[MyValue] ) / 2,
ALL ( MyTable ),
MyTable[MyValue],
1
),
MyTable[MyValue]
)

And it comes back with the largest number in my entire table, not just the TOPN. (10 in my test case).

I can't wrap my head around why this would be... can anybody help?
-Scott

 

[mole999]

MAXX Function (DAX)

Evaluates an expression for each row of a table and returns the largest numeric value.

 

[scottsen]

MAXX Function (DAX)

Evaluates an expression for each row of a table and returns the largest numeric value.

Parameters


[TABLE="width: 1496"]
<tbody>[TR]
[TH="bgcolor: #EDEDED"]Term
[/TH]
[TH="bgcolor: #EDEDED"]Definition
[/TH]
[/TR]
[TR]
[TD]table
[/TD]
[TD]The table containing the rows for which the expression will be evaluated.
[/TD]
[/TR]
[TR]
[TD]expression
[/TD]
[TD]The expression to be evaluated for each row of the table.
[/TD]
[/TR]
</tbody>[/TABLE]


TOPN returns the "table" for the first param... no?

 

[mole999]

I know nothing about DAX but its pretty clear that the intent is to return the Max value, and not the Top 10

 

[scottsen]

In case some crazy person comes across this in the future, this was actually confirmed to be a bug, by Microsoft. Not sure of full scope nor fix time.