Best Practices for to define list in Properties vs Modules

Highlighted
Occasional Contributor

Best Practices for to define list in Properties vs Modules

Hi experts

I am looking at the benefits of defining list in Properties and Modules.

Eg. The Pack Type Size members (Size) are to be tied to a SKU.

There will be inputs at Size (100g, 200g etc) and Pack Types (Small, Medium, Large) and calculations based on these inputs.

I thought I read it somewhere that it is better to define these in Modules but I can't find the writeup (or I could be imagining).  

Is there a best practise for these kind of situation?  If you have another way of doing it what is it and why ? 

 

Sally_1-1591138483885.png

Sally_0-1591138326452.png

Sally_0-1591138930967.png

 

Thanks.

 

 

1 REPLY 1
Highlighted
Valued Contributor

Re: Best Practices for to define list in Properties vs Modules

Hi @Sally 

 

Best Practice clearly states that we should not use List Properties and replace that with System Module for major hierarchical list and store properties in the module.

Your best guide for best practice is the Planual document found here 

Also, here is an explanation of why to use System Modules instead of list properties.
https://community.anaplan.com/t5/Anaplan-Platform/Planual-Explained-Day-5/m-p/69810#M13615

Einas
"Give a Man a Fish, and You Feed Him for a Day. Teach a Man To Fish, and You Feed Him for a Lifetime"