topic Re: Prevent spliting when using LYTD (pbix attached) in DAX Commands and Tips

Prevent spliting when using LYTD (pbix attached)

Anonymous — Thu, 23 Sep 2021 07:37:52 GMT

I have this pbix : https://drive.google.com/file/d/1tpGKvL_ST1L7YgDkDFqqLqfKb0FEjfcL/view?usp=sharing

I have a single selection filter on Year, and when I select 2021:

My goal is to never split a given Customer on Type, so, when I show the totals, I want to see: Net Revenue LYTD as 54 but in Locale, not in Inter:

I cannot harcode it... Many clients can belong to the same type.

Also a client changing 'type' can happen with more than one client in the future (or different type names). The only good thing is: if they switch, they do it on 01-Jan.

Re: Prevent spliting when using LYTD (pbix attached)

BeaBF — Thu, 23 Sep 2021 11:09:19 GMT

Anonymous If you want to see all the totals only on the "Local" type, why do you put the other types in key?

The purpose of your request is not clear to me.

Could you show the expected result and what you fail to do?

Re: Prevent spliting when using LYTD (pbix attached)

Anonymous — Thu, 23 Sep 2021 11:15:41 GMT

Thanks for your answer BeaBF ,

My expected output is:

(when 2021 is selected):

When 2020 is selected... it should work as it is already working:

Re: Prevent spliting when using LYTD (pbix attached)

PaulOlding — Thu, 23 Sep 2021 11:51:47 GMT

This measure gets your example result.

It first builds a table of Revenue LYTD for each inscope customer ignoring Type, then aggregates for the final result.

Net Revenue LYTD = VAR _CustomerLYTD = ADDCOLUMNS( VALUES(Revenue[Customer]), "@LYTD", CALCULATE([Net Revenue YTD], SAMEPERIODLASTYEAR('Date'[Date]), REMOVEFILTERS('Type') ) ) VAR _Result = SUMX(_CustomerLYTD, [@LYTD]) RETURN _Result