YOY in table card beast mode

Your Beastmode looks good, but you can't use the card's date selection because it is year specific. In essence when you choose 'This Month' then you filter out all data from last year.

Consider these beastmodes with no date filter:

`This Year`
CASE 
  WHEN YEAR(CURRENT_DATE()) = YEAR(`Date`) 
  THEN `Net Sales` 
END

`Last Year`
CASE 
  WHEN YEAR(CURRENT_DATE()) - 1 = YEAR(`Date`) 
  THEN `Net Sales` 
END

`Month` (for filtering)
CASE 
  WHEN MONTH(CURRENT_DATE()) = MONTH(`Date`)
  THEN 'This Month' 
  ELSE 'Other'
END

Then add a FILTER using the new beastmode `Month` and filter to 'This Month' which is not year specific.

@pauljames there are a lot of simple reasons that get in the way. Without more detail it is hard to say why that might be in your case.

First, the above formula lets you see them side by side, but to compare them it would have to be aggregated. The same record cannot be both this year and last year, but if you use a SUM to aggregate the rows it could compare the two.

-- `This Year`
SUM(CASE
WHEN YEAR(CURRENT_DATE()) = YEAR(`Date`)
THEN `Net Sales`
END) -

`Last Year`
SUM(CASE
WHEN YEAR(CURRENT_DATE()) - 1 = YEAR(`Date`)
THEN `Net Sales`
END)

Even that leaves lots of 'gotcha' concerns. The biggest one is grouping. Aggregate grouping is automatically affected by the card settings. In a table view all "non-aggregated" columns will form the group basis. So if you show Year(`Date`) as a column then each row can only use data from a single year. Nullifying the effect of the logic shown above.

This is hidden further in any other chart type. If you have a date grain on a bar chart for example, this will never work because a record from last year and a record from this year won't exist in the same date grain. Thus prohibiting the beast mode (which gets the data last after filters and grouping) from ever seeing records from both years to do math with them.