Hi,
Is there a way i can lock actual data when importing in Anaplan ?
I have changed the version edit from and edit to but when i test the import, prior period are being updated by my load.
Thanks in advance for helping.
Regards,
Tom
@tompatrickting22
'Edit to' and 'Edit from' is the best option to restrict the data feed into the specific versions. It should work.
But if it not working out, your can use the dynamic cell access as well. Create a module with a 2 boolean line items with the versions and use it as a Read/Write access driver. Whenever required you can lock the specific time periods for any version you want.
I hope it helps
~Anand
Hi @anand.shekhawat
Thank you for responding. I have already set the "Edit from" and "Edit to" in our Native version, but when I test to run an import, prior periods are still updated.
Am I missing something here ?
@tompatrickting22 ,
The import action will let you to import the data in all the cells if you have an administrator access of that particular model/workspace irrespective of the periods set in 'Edit From' and 'Edit to'. Once your admin access is disabled (like the end users) you can only import the data in the selected period only as set in 'Edit From' and 'Edit to' fields. The same goes with the Dynamic Cell access as well.
@tompatrickting22 As mentioned by @anand.shekhawat ideally you cannot restrict data updates via import. However if you really want the import to lock the Actuals data, I would create a transactional module as a temp module to load all the data via import from the source, then create a saved view with filters to show only forecast months and use this saved view to import into the main module wherein you want to lock actuals.
Hope this helps.
AB
Hello everyone, We are trying to use Anaplan Connect in order to push data from a dwh to Anaplan Data Hub. To do so, we need an authentication by token. We can't make it work, we receive the following error: ERROR 16020 |-- Anaplan API: Invalid key path Any suggestions? Thank you all in advance for the help! Michele
I am attempting to connect to an azure SQL database vis at the MSSQL connector in data orchestrator but am having issues and I believe it is due to hyphens in database name (which is a fairly standard naming convention I will note!) Example below (fake credentials) - has anyone else encountered similar and is there a way…
Has anyone found success using Anaplan XL with Polaris models in a shared drive with or without concurrent users? My team has experienced a variety of errors, login failures, etc. sometimes it works, sometimes it doesn't. We've been recommended to save and edit files locally, which helps but certainly with its limitations…
