Hi,
Just for my understanding, What I need to do in Anaplan so that when I change my current period (Q1) to next quarter (timescale Q2), my current quarter (Q1) data didn't not get delete and automatically covert to hard coded figures.
Thank you!
Hi @sharmagh
I agree with @mikejorg , you can control from Version Edit to & Edit From, Another approach to control is through DCA.
If you have ALM, then I think DCA would be better and faster, you don't have to sync every time.
1. Create one system control module by quarter and one line item
2. Create another Module for DCA
3 Apply DCA in your input module:
Hope this helps!
Thanks
Akhtar
Hi @sharmagh ,
As long as you aren't looking to change the model calendar, you should be able to adjust the 'Edit From' and 'Edit To' fields in the versions part of model settings.
It doesn't exactly hard code the periods outside of these fields, but it does prevent them from being edited.
@sharmagh Are you referring to the mechanism when you use on a version "Forecast the "switchover" flag?
I this case for "actual periods" the data are physically copied from "Actual" version on "Forecast" version and the previous "Forecast" values are lost. This mechanism cannot be changed.
What you can do is to create workarounds to preserve data of the "Forecast" version.
- copy data into another line-item that does not use "Use switchover" flag in modules before changing the current period
- create a custom mechanism to manage the "actual" and "forecast" months which does not use the "switchover"
etc...
I have this error message " Azure blob http error " when i save cloudworks connection to Blob Storage. I follow this link: Connect to Azure Blob | Anapedia Can someone help to identify the root cause and how to resolve? is it related to permission or security?
Hi everyone, I am trying to create a connection ADO from PostgreSQL, but I consistently receive the following error: Failed to establish a connection The following message was sent from the target system: The SSL certificate is either invalid or not in unencrypted PEM format. Please check your certificate and try again.…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
