Anaplan Data Orchestrator - Numbered Lists with Display Names

Question

Previously, we have used display names in system modules for our numbered lists and then referencing that from the list property for the display name. When using ADO though, that means creating links for each of the parts of the hierarchy as well as links to the system modules that contain the inputs for the display names. Would we be better off removing the link between the system module and the list property and just updating the list property directly? Is there any information on best practice here?

SHayes · Answer

Thanks James,

That makes sense but does create quite a bit of additional overhead in building out the processes unfortunately. In our case, we are pushing data from ADO straight to the Spoke model and bypassing using the data hub so directly updating the Spoke hierarchy

vanreign · Answer

Hi @SHayes,

Great question. Best practice remains, irrespective of IDO, that the source of truth of the display name be kept in the SYS module. This makes it scalable.

So, import processes are DH → Spoke Lists, DH → Spoke SYSs, Spoke SYSs → Spoke Hierarchy Build, List/Hierarchy Maintenance processes

Also, it is important to always question why a numbered list rather than a flat list is being used at each level of the hierarchy.

Cheers,

James