LAG function constraints don't allow for some valid scenarios

AnaplanIdeas

I would like to submit an enhancement request for the LAG function to be used between time ranges that are not the same but have valid overlap.

 

The constraint that disallows the use of LAG between any line items that do not have the same time range gives the function minimal utility. I understand disallowing instances where the timescales do not match (i.e. trying to pull data from nowhere), such as using a current-year time range to pull from a future-year time range, but not allowing use where that is not the case (e.g. LAG(Prior Year Line Item, 12, 0) on a current-year time range) is unduly handicapping.

 

As an example, a function that would be: LAG('Metrics'.Actual, 36, 0)

 

Has now become: 

PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS(PREVIOUS('Metrics'.Actual)))))))))))))))))))))))))))))))))))).

 

This greatly simplifies the ability to reference previous periods from other line items/modules, eliminating the need to repeat PREVIOUS() functions and allows for overflow calculations.