-
Custom Version Best Practices: Sales Forecasting and Planning Models
Hi all, I'd love to hear how you've successfully implemented custom versions in your organization. Please share your experiences or any resources you know of that outline best practices! I've seen two common approaches in the models I've worked in: Most common: Custom versions are a dimension in nearly every module. Most…
-
Changing formula scope does not re-apply to line items?
I have a formula which was written with the formula scope set to 'All Versions', then realised that I only need it to apply to 'Current Version', so I changed the scope but the data is still showing in the actuals and the forecast (all versions). If i add a new line item and set the scope first, and then use the exact same…
-
"Fake Versions", vs. Native Versions. How do "Fake Versions" work and how do you set them up.
A lot of organisations seem to use "Fake Versions", vs. Native Versions. How do "Fake Versions" work. Please could someone explain how to set up and use "Fake Versions", How they should be used and of course how they work (the logic underpinning them). Thanks
-
Native YTD Calculation issue
Hi, I have various forecast versions and a prior year version. I want to do a comparison between the selected version and the prior year version. I am finding that the YTD time summary for the prior year version is not taking the YTD as determined by the selected version. You can see that the YTD calculation for Current…
-
Importing same data into two versions - best approach
Hi, I need to import the same data into two versions (there are more than 2 versions, but only 2 are applicable for this requirement). I could have two independent import functions to import the data twice, once into the first version and another time into the second version but this is a slower process for the user.…
-
Regarding the versions
when we want the Actual version data of particular line Item to replicate into forecast version without using any formula or switchover.
-
Actuals that change according to Versions
Hello, I am facing an issue regarding Versions, and I was wondering if there are new ways to resolve this. I have looked into this thread, but it is from 3 years ago, so I was hoping for an update on the matter… I figure I can’t be the only one.…
-
Гигиена моделей - время уборки
Всем привет! Мы восстанавливаем активность в группе, ведь весна - время обновления. И ваши модели не исключение! Есть много причин провести гигиену и оптимизацию моделей, особенно если им несколько лет. Если вы решились на «генеральную уборку», вот на что стоит обратить внимание: Старые костыли и «брошенный» функционал…
-
Different formula for different selected version
Hi, I have 5 different versions in my model, Actual, High, Low, Mid, Budget Q and Budget FY. I need to apply a lag a figure one month to the first 4 versions and for version Budget FY, I need to take the months value not the lag. I have configured a custom versions module as well as attempted a boolean approach but am yet…
-
1.02-05 Try and avoid a high number of native Versions
Versions have built-in functionality that is not available for normal lists. However, a large number of Versions (e.g. 10+), can have performance implications due to the block structure. Review the need for high number of Versions, and if the native functionality is not critical or needed, consider using a normal list to…
-
1.02-01 Use "Current" in Version settings
Utilising the Current (and Actual) check box within the Version Settings allows the use of CURRENTVERSION() and ACTUALVERSION() in calculations, in SELECT statements and ISCURRENTVERSION and ISACTUALVERSION() for Boolean checks. Current version also acts like a top level for Versions; if you have a source module with…
-
1.02-02 Do not use formulas in the version settings
Whilst this is a simple construct and it might be OK for simple models; it effectively adds size to models every time versions are used in a module even if you don't want the variance. Also, in modules with 3 or more dimensions if you have calculation line items and aggregations the results may not always be give the…
-
1.02-04 Always move switchover dates forward
Using switchover means the historic periods are effectively cleared out. This does have the benefit of reducing model size as the historic cells are cleared, but switchover should be moved forward only. Moving it backwards will blank out the respective period removing any values that were previously held
-
1.02-03 Edit To / Edit From
Use these as a simple, administrator lead control for read and write access to versions. For more granular control use Dynamic Cell Access