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

 

Best Practices article: 
Top Level Item and Parent Hierarchy

Tagged:

Comments

  • 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.

    Misbah_0-1599545265599.png

    Misbah_1-1599545274178.png

    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:

    Misbah_2-1599545303804.png

    Misbah_3-1599545308242.png

    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.