About DouglasEaton

Hi Ryan, I believe the only solution in your predicament is to store the actuals per version. Because you effectively want to track changes in actual periods for different versions, hence the need to store those somewhere. Unfortunately that also means getting rid of the switch-over. This is what I have in mind: Pre requisite: 1) Store your actuals in a new module dimensioned by version (let's call it Actuals per Version) 2) Untick the switch-over boolean 3) Change formula scope to Current Version only, it's not mandatory but would make your model more efficient New Formula: If item(time) < Version.Switch-over Period then Actuals per Version.Amount else Forecast Calculation It's not perfect but it should solve your issue. Hope this helps Doug ... View more

Hi  Takushimozuru,   Yes you can. The easiest option is to use another list as your new Code format (Any Code list property in your example). Once you've got that you will need a mapping table between the list you used for your new codes and your Initial list (Test in your example). This mapping will be in the format of Test and applied to the new code list. The formula to used to create this mapping table will be Test.Test Item[firstnonblank:Test.Any Code] (Test.Test Item - this property needs to be created and is simply ITEM(Test)) Once you have created the mapping table, all you have to do is to reference it using a LOOKUP function to retrieve your Test list items in your module.   It is also possible to do it with free text as your new code but it takes more space and requires additional calculations so I would advise against it if you can. If not here below is an example of how to do it. Note that the Flag I'm using in this example is simply a List named "Flag" with one member in it also named "Flag".   Let me know if it's not clear.   Cheers                                                       ... View more