Old idea that needs attention: Formula scope on combination of Actual and Current version

maud_vermeulen

This request has been posted already in 2013  & 2018 and probably in the years in between. It is not availbale yet, while it will solve a lot of problems for many of our customers.

If you do not want to change a previous version, then the option for Formula Scope needs to be put on "Current Version" this however blocks all formulas that use IF ISACTUALVERSION().

#FormulaScope #VersionControl

Miran

Status changed to: Not Planned

Rebecca

Status changed to: Not Planned

Gwen.pryor

Status changed to: Not Planned

mhemphill

I think this one reopens the debate on Versions or Fake Versions.  If you use Fake Versions then it behaves like any other list/dimension. You can then do anything you wish using simple property module with boolean for:

 

Actuals?

Current Forecast?

Budget?

 

 I think this Version thing was invented as a short cut for self-build customers who didn't want to have 'proper' developer on site. I know many projects not using Versions at all. ****-hum

Fake versions can of course be list formatted and subsets.

maud_vermeulen

Dear @mhemphill

 

How do you create lines then where both a calculation is available (for actuals) and input for the forecast months? 

We also decide per model what to use and because of the issue with native versions we move more often to dummy versions. Which takes away some of the advantages of the switchover functionality.

 

Kind regards, Maud

 

 

 

mhemphill

@maud_vermeulen 

 

Hi Maud.  

Never been a great fan of a cell having two states - formula and input. Two states is the world of quantum computing 🙂  Its not very DISCO either.

 

But,

1. Extend the Actuals loading work so it also targets the actuals months of the Forecast module(s). 

2. Overlay month specific DCA to achieve switch-over

 

Hope that helps

 

M