About MarkTurkenburg

Hi @anirudh    Thanks but that doesn't work for the following reasons:   - I wish to have 2 or more Live versions running at 1 time. This means I need to keep the formula scope on Line Items set to All except Actual or All Versions. This means I cannot import directly into them as below - This is a time consuming method as you need to create import processes for each module (which may run up into the 100's)   So my current workaround of creating PLAN modules which are a copy of the original module, removing the line item formulas and then importing into them is the only solution. This is quite a shortfall of Anaplan, I'm surprised I thought there would be a better solution to what must be a common problem   Thanks    ... View more

Fantastic @anirudh    How do I import a Static Version?   Many thanks   Mark ... View more

Hi @ArunManickam    Thanks but the read only version STATIC PLAN (I'm assuming you make it read only in the User Section or DCA) will still be effected if a formula in the model changes. Read only will only prevent the user from changing data but I require the values to be effectively Hard Coded so even if the model is improved the original values remain   Mark ... View more

Just another point but very important, using DCA/Fake versions etc to lockdown a version means that you can not change the model structure - e.g. formula adjustments at any point will drive movements in your Plan version. Our models are constantly evolving as we seek to improve them and hence you need to be able to hard code your Plan version that may of been created 10 months ago, before multiple model adjustments have been made   Thanks   Mark   ... View more

@rob_marshall    Thanks but I don't think that is relevant for my query. I'm wanting to lock down/hard code values in a version & I can't see how using a Fake Version dimension would assist in accomplishing that as you essentially you end up with the same problems as with the native Version dimension (see my last post to Arun)   I might be over-thinking it but I would imagine that a locked down/hard coded Plan/Budget version and then a Rolling Forecast version and possibly additional scenario analysis versions are required for a high percentage of FP&A models within the AP ecosystem. It obviously works fine if you only require 1 Live model as you can set the Formula scope to Current Version but once you move to greater than 1 live version it seems to become very difficult   What would be fantastic is the Formula Scope option to be able to set to a number of Versions, possibly referenced by a Boolean like with DCA. This would by-pass all of this   If my only option is DCA then I think it is better to create copies of the relevant modules, rename them Plan, remove the Version dimension and import the data from the Plan Version & then apply DCA. You can then to create modules for Variance analysis between the Version being analysed and your Plan but at least there is no chance that the plan numbers will change. It is far from ideal but currently that is my only solution   Thamks ... View more

@ArunManickam  I think I need to step it out as I haven't explained myself clearly but I think the situation is as below:   - Ideally I would like to have a Plan Version where the formulas have been locked/hard coded. Eg you create the Version like any other version but then you can remove all the formulas so only the values remain. Then you could apply DCA to guarantee that not adjustments will be mistakenly made. This ensures that the data never changes and there is no need to track down a movement if it occurs. As you know models can become very complex & a movement can come from many places (e.g. Sub-Set adjustment, List Property adjustment, Formula adjustment) - Then I would like to have a couple of Live Versions where the formulas are working etc   - From what I can see this is not possible, what is possible is:   - I create the Plan Version and be make sure that every line item references also contains Version as a dimension. This way when you apply DCA against the version you will not be able to adjust any values but this also carries it's own risks, being:   - You cannot adjust any formulas within the model as any adjustment will drive a value change in the Plan version. We are constantly changing/adjusting our model and any formula adjustment will drive a movement to the original value even if DCA is applied -  I would need to create separate Sub-sets  for this Version only because if the subset changes in the future, the data in the module which references the sub-set will change even though DCA is applied because DCA does stop any formulas, just input from the user - You need to make sure that your list properties are certain not to change in the future because any adjustment in a List property that references a list item in your locked version will cause an adjustment, even if DCA is applied   Do you agree with my summary or have I gone down the wrong path?   Thanks for your help   Mark ... View more

Hi @ArunManickam    Thanks but DCA doesn't stop/freeze calculations, it only prevents the user from adjusting the values?   If so this means that you have to make sure that all your variables etc are running off Version as a Dimension, otherwise if 1 changes it will change your locked down version?   Thanks   Mark         ... View more

Hi @anirudh    Ok - so you are saying to keep the version 'Live' as in all the formulas are still operational but they will be protected by DCA? My definition of locked down is that the data no longer has formulas but the values remain   I think your idea is fine but it means you must have Version as a dimension on every driver (because it needs to remain static for the Plan version) and also you cannot really use List Properties as you require the ability to hold some data constant while others remain dynamic   Have I correctly interpreted your answer?   Thanks ... View more

Thanks @ArunManickam    I'll keep it in the mind for future data integrations   Mark ... View more

Thanks @Jared Dolich    It's not currently an issue for me but was just thinking about how you could confirm completeness of uploads with large data sets. I could definitely see scenarios where 1 or multiple Source items are slightly different to the Target etc and it would be difficult to determine whether the full data set has been imported    You could always create Dummy list item in the data source which is the SUM of all the other list items the source. You could then create a module with this item mapped through and compare vs the results from the upload module to identify variances    Think it would be helpful for Anaplan to have a native solution for this because it doesn't matter how fantastic the calculation engine is if the source data is incorrect!   Mark   ... View more