List properties are the same as line items, but have many limitations, so keep it simple and have one place for calculations i.e. Module.Line Item
Best Practices article: Data Hubs Purpose and Peak Performance
Rule 1.05-03 Avoid using List Properties List Properties are same as line items but have many limitations, so keep it simple and have one place for calculations i.e., Module line items. This goes against P and A of PLANS if you wish to create list properties.
Here is how it was done in Pre Planual Era: Whenever there was a need to have an attribute to the lists we used to create list properties.
What is wrong with this method? There are two disadvantages of using list properties.
Here is how it should be done in Planual Way: Create a System Module for each list wherever you have properties associated to the lists. This will be a centralized place to store the attributes of the lists. It is worth to mention that these system modules should not have additional dimensionality – No Time, No Versions, no other lists.
Exceptions: There are 5 exceptions that have been given by Planual where you can use List Properties and here is the detailed explanation about all these exceptions
Without Row Labels – By default list Name will be available in the labels
With all Row Labels i.e., Name, Code and List Property called Order
4. 1.05-03d Conditional Dashboard Navigation: In Classic Dashboard list properties are used to help navigate from one dashboard to another. For example basis the Order list property value different dashboards are being opened up
Read more on Anapedia link Open Dashboard
5. 1.05-03e Dependent Dropdowns: List Properties are needed to create Dependent Dropdowns
Here is the micro lesson on how to create dependent dropdowns Dependent Dropdowns - Anaplan Community