How to use a different 'Current period' for different versions

I'm working on a model with three versions: Actual (Actual version), Scenario: Prognose lopend jaar (current version), and Scenario: Budget volgend jaar.

For one of the calculations, the Scenario: Prognose lopend jaar version needs to use a different current period than the Scenario: Budget volgend jaar.

For this, I created a module with the Version dimension and a Current Period line item with the formula: IF ISACTUALVERSION() THEN TIME.'Current Period' ELSE IF ISCURRENTVERSION() THEN TIME.'Current Period' ELSE 'M_SYS03_Tijd instellen'.Current period voor Budget volgend jaar

The calculation must transfer the actuals from the desired current period to future periods, with the current period varying for each version:

So, for the Scenario: Prognose lopend jaar version, the actuals from February 26 (orange) must be carried forward to the months March 26-December 26, and for the Scenario: Budget volgend jaar version, the actuals from January 26 (green) must be carried forward to February 26-December 26.

This works well for Scenario: budget volgend jaar, but not for Scenario: Prognose lopend jaar.

When I drill down, I see the following in Scenario: Budget volgend jaar:

and for Scenario: Prognose lopend jaar:

If I determine the current period per version manually instead of using a formula, it works fine for both versions.

Can anyone tell me what I'm doing wrong and help me automatically enter the correct values?

Accepted answers

alber818

Hi All,

I submitted this case to Support. I don't really have the answer I had hoped for, but this is their final response:

After reviewing your setup, I would like to clarify that the issue is not with your formula itself, but rather with how the version-related functions (ISACTUALVERSION() and ISCURRENTVERSION()) behave within Anaplan—especially when combined with switchover and current period settings.

What is causing the issue?

Your current logic relies on:

ISACTUALVERSION() to identify the Actual version, and

ISCURRENTVERSION() to identify the forecast/current scenario.

However, there are some important limitations:

ISACTUALVERSION() inconsistencies:
This function may not always behave as expected when switchover is enabled. In some cases, it can return unexpected results and does not always align correctly with the model’s current period.

ISCURRENTVERSION() limitation:
Only one version can be marked as “Current” in the model at any time. This makes it unsuitable for handling multiple scenarios with different “current periods.”

Key observation:
Since your logic works correctly when values are manually set per version, it confirms that the issue lies specifically in how the current period is being derived—not in the calculation itself.

Recommended solution which might fix the issue:

To ensure consistent and reliable behavior, we recommend avoiding these version functions for this use case and instead storing the “current period” explicitly per version.

All comments

devrathahuja

@alber818 - Hi, I tried to recreate it and it's working fine also with calculated values-

I've only taken the false criteria since drilldown shows the boolean is false in your case for both.

Can you attach the screenshot of the blueprint view of the line items? Additionally, can you create a new line item (line item abc) and add the same formula as your original line item referencing the calculated time period and see if that shows values?

alber818

Hi devrathahuja, thanks for trying to help me!

I copied your formula and then it gives the result I expect:

But I'm not sure if this solves my problem, because it looks to me that the problem is in the SYS03a Tijd instellen - Versions module. When I use a formula to calculate the current period for a specific version, it always goes wrong.

You only used the false criteria, but it is important that when it is TRUE the realization is taken from Actuals.

This is the blueprint you asked for:

Can you show me what your SYS Versions module looks like?

devrathahuja

@alber818 Hello,
I am also using a formula to calculate the time period, in fact almost the same one as you-

Just hardcoded the Jan 26 here for a rough example^

What happens if you refer to the calculated line item lookup in a new line item? So exactly what your formula is but in a new line item instead?

As for the blueprint view, can you share this section-

Maybe it has something to do with the formula scope or other version settings specific to the line item?

Can you also add the first part of the formula so I can replicate both the conditions & see if that helps spot the issue?

alber818

Hi devrathahuja, I think the formula scope and other settings are correct, see below.

When I refer to the calculated period lineitem as you asked the original problem appears again :(

I'm not sure wich formula you want to see, but here's one:

another one:

and the last one:

devrathahuja

@alber818 - Hi, thanks for sharing.

I want to see this part of the formula-

Can you also add the formula for realiste huur line item?

alber818

Hi devrathahuja,

This one is filtering wich months are 'Actuals' and wich months are after a custom switchover:

and this is the formula for the Realisatie - huur lineitem

It's quite a challenge, isn't it?

devrathahuja

@alber818 - It indeed is!! 😅

What happens if you change the formula in current period 2 (formula) to refer to current period 1 instead of calculating it through the logic? Does it still show 0s?

Additionally, if you create a new line item current period 3 (formula), add your original formula here & use this in the lookup, does that work?

I tried also with the IF statement & it shows correctly for me-

alber818

I've tried your suggestion: created LI Current period 3, that uses Current period 1 (Manual). And when I use that new LI to test the forecast it works well. So the final test should be to use Current period 2 (Formula) for Current period 3 and see if it still works.

But unfortunately then the old issue occurs again. So the thing that causes the trouble must be in LI Current period 2 (formula). But I have no idea what it is ☹️

devrathahuja

@alber818 - Yes you are right, it has to do with that line item in particular then, not sure why either? What is strange is that it also works fine in your case when you refer to the manual line instead which both show the same months!

I look forward to hearing from you in case you get to the root cause of this :)

In the meanwhile you can btw optimize that formula to say-
"IF ISACTUALVERSION() OR ISCURRENTVERSION() THEN xxx" since the first 2 IFs lead to the same outcome

alber818

Yes, I also saw that optimization while changing and testing some things.
When I have the solution I will share it here.

Thanks for your help!

devrathahuja

@alber818 - Hey,
I think the issue somewhere lies in the actual version in your realisatie line item since in here we see that the actual is blank-

But realisatie line item has values for Jan,Feb,Mar26 so actuals should be showing for both the cases instead it shows up as 0.

You can try these 2 things (after which reaching out to support might be the best haha)

1.In the testdevrathahuja2 -
Try formulating it as IF isactualversion() then realisatie…. else realisatie[lookup: current period 2 (formula)]

2.Create a new dummy test line item with source values and manually add the 2830 in Jan-Mar for act version

Then if you have a new line item which says ACT[lookup: current period 2 formula]

Maybe 1 of these 2 works & helps narrow down the issue?

alber818

Hi devrathahuja, sorry for the late response, I had to do some other things. I've tried your last suggestions, but still no success. I think reaching out to support is the next step to hopefully solve this.

Thanks again!

alber818

Hi All,

I submitted this case to Support. I don't really have the answer I had hoped for, but this is their final response:

What is causing the issue?

Your current logic relies on:

ISACTUALVERSION() to identify the Actual version, and

ISCURRENTVERSION() to identify the forecast/current scenario.

However, there are some important limitations:

ISCURRENTVERSION() limitation:
Only one version can be marked as “Current” in the model at any time. This makes it unsuitable for handling multiple scenarios with different “current periods.”

Recommended solution which might fix the issue:

To ensure consistent and reliable behavior, we recommend avoiding these version functions for this use case and instead storing the “current period” explicitly per version.

Quick Links

Can you help?

Unanswered questions

Looking for Anaplan End-Users to take a short survey!
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
Top-Down Allocations
Estimated Level of Effort:4-8 Hours of Model Building Level of Difficulty: Beginner Recommended Training: L2 Model Builder Training Persona: Casual Model Builder Potential ROI: Decreased planning time Increased accuracy of targets/spreads You Might Also Like: * Historical Snapshotting Top-Down Allocations Whether it's…
Historical Snapshotting
Estimated Level of Effort: <4 Hours of Model Building Level of Difficulty: Beginner Recommended Training: L1 Model Builder Training Persona: Casual Model Builder Potential ROI: Decreased response time to address risks Increased forecast accuracy You Might Also Like: * Tops-Down Allocations Historical Snapshotting One of…