But I don't think it's necessary to write this function in every diagram. I tried to filter the Value directly in the script, but it was wrong no matter how I wrote it.
Personally I would tend to a logic like the following by adding a more suitable period-field which isn't:
year(date) * 100 + month(date)
else
year(date) * 12 + month(date)
because with it you could always calculate the offset between two periods directly even by the turn of a year.
Afterwards you could apply something like this:
... where Month1 > X and Month2 < Y and Month1 - Month2 = 1;
whereby I think I wouldn't apply a hard filter else using the offset-calculation as flag-field - later used within the set analysis and/or as selection within a list-box.
Personally I would tend to a logic like the following by adding a more suitable period-field which isn't:
year(date) * 100 + month(date)
else
year(date) * 12 + month(date)
because with it you could always calculate the offset between two periods directly even by the turn of a year.
Afterwards you could apply something like this:
... where Month1 > X and Month2 < Y and Month1 - Month2 = 1;
whereby I think I wouldn't apply a hard filter else using the offset-calculation as flag-field - later used within the set analysis and/or as selection within a list-box.
I think the operators and the order between the conditions aren't correct and might look more like:
Where Month1 - Month2 = 1 and ((Month2=202203 and Month1>202203) or (Month1=202201 and Month2=202112));
Within the UI you may reach just with the mentioned offset-flag, like:
sum({< Flag = {1}>} Value)
and selecting the wanted periods either from Month1 or Month2 because both information will interact with each other. Depending on your final requirements you may need some extra logic like querying for the current period and/or for cases where the flag becomes negative or ...
