Announcements
No record found.
HI
could you tell me what are the limitations & constraints in using a Custom Entity rather an out of the box entity?
*This post is locked for comments
Hi Tavares,
Are you using online or onpremise?
If it's online refer the following blog:
www.palmettotg.com/.../how-do-i-view-or-increase-my-storage-limit-on-dynamics-crm-online
Hope this helps.
Regards,
R.Rajkumar
"Please mark my answer as verified if you found it helpful"
Hello,
I'm using online.
actually, I'm looking for functional limits in order to decide if I should choose a Custom entity or an ootb entity.
Hi,
Refer the following thread:
community.dynamics.com/.../101280
Using out box entities are always good option and considered as best practice, because they will provide you some of the functionality out of box that you won't get with custom entity for example email template, out of box relationship mappings, activity rollouts etc.
So it is always better to first map your requirements with out of box entities, if you can't then go for custom entity.
Thanks
Custom Entity if you choose it over such as Account, Contact, you will no longer get the capability in term of Customer OOB Entities, such as for Activity, Case, Marketing List, Opportunity potential customer, Customer Address, etc.
Then you also need to build the functionality such as ribbon, plugin, workflow, and Business Process flow.
But, sometimes we need to create this, the reasons are can be because the entities you need are not existing ones, CRM doesn't have this, for example your Custom Master Data, intersect table, etc
Other reason why need creating also for example very limited oob functionality for let's say Competitor entity or sometimes you need to create Contract custom entity, because totally different functionality.
Usually Account, Contact, Case, Opportunity, Quote, etc, I will still use them instead of creating new entities considering better you rename it than you create new one.
You may refer to this also:
www.avastonetech.com/.../CRM.aspx
Hope this helps, thanks.
If you have the option to choose between custom and standard entity, I would suggest you use the standard entity, since if you get a new crm update, and there is new function for this entity, you will also get it automatically.
My purpose is to manage an other kind of contact. I already have "end-user" supported by the Contact field and now I have to manage relationship with kind of upper level contact. Do you know (in order to use standard entity) if it makes sense to use a Contact type ? meaning to have one Contact entity with different forms?
Yes, you can have a simple dropdown field for contact type and you can use the same form, but if you think there are much difference in two forms with respect to the fields you can setup different form, otherwise can work with simple form and hide fields using business rules or js code.
Thanks.
Yes I would do that. Because the processes you use are processes for contacts.
You can use business rules to show / hide fields which are only relevant to this contact type
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
JS-09031509-0 3
AS-17030037-0 2
Mark Eckert 2
