Entity Creation best practice

Khaleelah
Khaleelah Customer
10 Comments 5 Likes 5 Up Votes Name Dropper
in Platform

Hello Team,

We are faced with an issue whereby we have multiple entities in a hierarchy.

Now the screen using these entities will not load unless we restrict data from the higher level entity to one selection only. Meaning by default the screen is set to one Brand for example.

What is the best practice when creating entities if we have many related to each other.

The above scenario i have described does not suit the customers requirement as they would need to work with multiple brands at the same time for analysis purposes.

Any guidance on above

Thanks

Answers

  • Adrien Albrespit
    Adrien Albrespit Employee
    10 Comments 5 Likes First Answer Level 300: Expanding Board in Your Organization

    Hi Khaleelah,

    Regarding the problem that you are facing loading your screen, the reason is probably not related with your entities structure but more likely with the volume of data that you request Board to load and display in a single request.

    As you mentionned, the first solution to avoid that can be to limit the data that must be retrieved and displayed using selections. If your Parent entity is not relevant to be used as a selection, you can try to think of another (at other level or on the same tree but in a different branch of your tree to limit the number of Child entities. For example: All P.Divisions are useful however so we can't use them as a selection, however, we can limit the number of finally Products displayed selecting only some P.Categories

    image.png

    Other option will be to aggregate the results on the screen that you try to load on a upper level. If the user action must be made at the lowest level, you can consider using drills downs to perform them.

    Best regards,

    Adrien

Categories