Hi,
Can I create logic that only allows end users to perform an Import Action if the today's date has not passed the deadline?
Best regards,
Johan
@johan.marketoft
There is no native functionality in Anaplan to populate Todays date. It can be achieved via a daily import driven via Anaplan connect however.
You will need to take a use input or the import from a schedule Anaplan connect action and use this to create a logic which will prevent writing into certain time periods.
If the data comes from another Anaplan model then you can simply filter out the dates. If it comes from an external source then I would use dynamic cell access and turn off write access into those dates.
Good luck,
Chris
yes: your import action MUST be controlled by a view which is controlled by a boolean (that MUST be the standard for all your imports).
In this boolean you ca simply compare against a today's date line item vs deadline. Even if the user runs the action, it will do nothing.
If the action is from a file, the only way is to do a staging first and then the controlled view logic.
Yes consider creating a boolean "Past Deadline?" that specifies, "Is today's date past the deadline?", and then another boolean that says "Import?"
The "Import?" line would have a formula along the lines of, "IF NOT 'Past Deadline?' THEN TRUE ELSE FALSE".
Then your import action will still "run" but will be depndent on the date if your data pulls over.
I wanted to check if others are facing this specification difference between Grid Card in Additional Insight. When created using a Saved View, the Quick Sum bar feature does not work, but when created using the module directly, the Quick Sum bar works.
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
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…
