1 of 1 people found this helpful
IF SUM([Value]) = WINDOW_MAX_SUM([Value]) then "Y" else "N" END
Restart that every [account #] if you want the max per account. Otherwise do the calc for WINDOW(down) to get the max across all accounts.
And if [Value] us already an aggregate, then you don't need to do SUM[Value]). Just use [Value]. So some of this answer comes down to, "It Depends..."
Having an actual workbook would have let me address those "it depends" factors.
Thanks Joe, this works great. Is there a way to make this calculated field work on the data before I bring it into the view? So that it's essentially a part of the initial data table.
I'll gladly try and mock something up with superstore if needed, and if I can.
You can probably do it with LODs.
Hack up your existing data. Check out this video:
Grab rows for about 5 accounts. Just a couple of rows per account. Keep the minimum number of columns to demonstrate what you need. (We don't need addresses or names or geographical info, for example. Just keep 3 columns: Account, Code, Value.)
I got bumped to another project, but I'll come back when I can. Thanks again.