Current v Prior Variance

Hi Community.

We have a situation where the Current v Prior Forecast Year to Date number is meaningless, and we would like to fix this if possible.

It so goes like this, example

Current calculates YTD to Week 34

Prior calculates Year to Date to Week 32

So if we look at the var to Prior forecast the answer is meaningless because different figures are being compared.

how can we (or rather me!) stop this happening?

Grateful of any answers or ideas, and sorry in advance if I missed this when doing Part 1!

Chris.

Accepted answers

U can use Lag Formula and Lag by X weeks

Hi Wedd26,

Good idea which I tried.

I used the LAG function in the formula box of the 'Current Vs Prior Fcast' version and pulled the error of having to reference a timescale.

Thanks though.

RANKCUMULATE not working when adding additional dimensions to module
I have an issue where I am getting the expected result from RANKCUMULATE when using one dimension, but when I add an additional scenario dimension to the module, it doesn't calculate the way I'd expect. Here are some screenshots to explain the case: Module 1 - calculates cumulative total for list items in list "Age"…
Introducing Anaplan API Python SDK
Hey everyone, I wanted to share the Anaplan Python SDK with you. It's a Python Library that wraps all Anaplan APIs and makes it easier to interact with Anaplan programmatically. It is mostly designed with Data Integration Scenarios in mind, but it does support all APIs including ALM, SCIM, Audit, and Cloud Works. Please…
Cloudworks Big Query Integration Fail
Hello, I am receiving an 'Anaplan Upload Failed' Status Description when testing my integration with a Big Query dataset. The integration imports data from BQ to our Anaplan model. No other details given in the error log. I suspect that Cloudworks is not even picking up the file but am not sure what we did wrong on the set…