Only use Top level for lists that will need sums so not Currency codes, or True/False (Indicators), or children in composite lists
Best Practices article: Top Level Item and Parent Hierarchy
Rule 1.05-06 Only use Top Level for ultimate parent Only use Top level for lists that will need sums so not Currency codes, or True/False (Indicators), or children in composite lists
Here is how it was done in Pre Planual Era.
What is wrong with this method? It is not required at all. Because you are not going to aggregate the values based on all the currencies as the output won’t make any sense. Also the system will aggregate unnecessarily making that extra second delay impacting performance
Here is how it should be done in Planual Way:
As a thumb rule we don’t use Top level for lists that are not meant to be aggregated. Like currencies, Indicator lists or any other list which need not be aggregated.