account dim(design)

[Former Member]

HI Friends,

I have multiple plng applications. which is best practice between below 2.

Using separate account dims for each application or using single dim for all applications.

Could anyone guide me based on volume comparison?

I have seen one case where all applicaitons are using single account dim, whose members are around 1500, but trying to add properties system taking so much of time, even not allowing to add properties. If it the case, can i use it account dim as owner dim in work status definition.

thanks.

[Former Member · Accepted solution]

Hi Naresh,

The way you want to design applications, dimensions, members and properties, actually depend upon your scenario and requirement . For eg. you can seggregate as: 1. Sales Application, 2. Planning Application where you have various dimensions which are required to you in each of the application.

But, we do need to have these dimensions:

Account, Category, Time and Entity compulsorily in each application set.

You can associate different members with each of those dimensions and the properties of members.

There is no limit of dimensions, members and their properties but it is advisable not to increase their numbers unnecessarily as it might slower the performance of system.

Hope this clarifies.

Regards,

Poonam

[Former Member]

resolved.

[Former Member]

Hi Naresh,

If you are going to use same members across the applications, its better to use same dimension. However, if the applications have different members, then you can use separate dimensions for your requirement.

As you have correctly noticed, a huge number of members may slow down the performance. So, keeping this in mind, you need to consider the implications of having the members in a single or in separate dimensions.

Hope this helps.