Dynamics Community Forum Thread Details

Pros and Cons of a 1:1 relationship vs add everything to the Account entity

Should I create a new entity or simply use the Account entity

Basically looking at the metadata, it is a type of account.

There are fields that is specific to this type of account, and it also requires a list of views just for this account type.

I know it is totally achievable to keep it just as an account type and just add a dedicate tab / views and etc. just for this type

At the same time I also know, if I create a new custom entity with a 1:1 relationship with Account.

I can keep the form a lot simpler.
There will be less fields on the form, less views for users to work with.
All correspondents will be specific for this new entity instead of lost in all other correspondents regarding the general account entity.
I can control the user privilege by only using a security role instead of adding field security or JavaScript.
On the Ribbon (yes we are still using the classic web UI), user will get the new entity as the tile, quick search will not bring back other types of Account.

Someone said to me, it's better to keep all accounts together regardless of their type. So metadata will be kept in one place instead of 2 separate tables. But for me that's the whole point of splitting it into 2 tables is, for users who is only interested in the type A can go straight to entity A. but for user who is dealing with none specific type accounts can still get all info from the Account entity.

As you can see I am really in 2 minds here.

Love to hear your thoughts on this.

Many thanks in advanced

Quick Links

Leaderboard