HI,
From a model builder point of view, what are the best practices to follow in order to understand an Anaplan model built already when there is no documentation available (no design docs) nor technical knowledge transfer?
Thank you in advance!
@Manuela_Apostol
Kind of depends how well the model was built. If they followed the best practices it will be easier, but I'd follow the steps below:
1. Look at Dashboards to try and get a feel for the process and flow for the users, understanding the modules and dimensions as you go along
2. Use the model map and search the the ending module(s) from 1. , use the "selection" option to isolate the links in and out. Hopefully zero or now feeds out
3. Repeat 2 as you build up a picture for the data flows back to the start and then look for any modules housing data and attributes
4. Look at the actions in and out to see what data comes into the model, from where and where does it go to?
5. You can use exports of the blueprints for line items, modules, actions, lists, etc. to see what is being referenced where
This is exactly the reason why we advocate the PLANS modelling best practices to help in situations like this. Logical and structured models with single purpose modules are much easier to audit and understand. If you aren't familiar with what I mean, look at this page and the links below for other articles supporting the subject
PLANS - This is how we model
I hope that helps
David
Thank you very much @DavidSmith!
Hi Community, I’m encountering an issue where an export created in Anaplan is missing column headers when retrieved via the API. However, when I manually run the same export from the Actions tab, the downloaded file includes the headers. Has anyone experienced this behavior before? I’d appreciate any insights into the root…
When importing data from a Data Hub to another model, I'm seeing values in the target model that don't exist in the source. For example, seller assignments are being tagged with subregions that aren't present in the source data - some assignments are missing expected tags, while others are mapped to seemingly random…
Hi all, I, as an Anaplan workspace administrator, am working together with a Fabric team to export data from Anaplan to Fabric via Anaplan API and Postman. We have a problem where all Anaplan exports are visible in Postman but when trying to connect to SOME of them, we get message "404, Not found". Below screenshot showing…