We had a potential customer contact us with a unique problem – they were building out their Dynamics CRM solution, and they encountered the limit on the maximum number of fields an entity can have well before they were finished adding all the fields that were needed. Out of the box, the Account entity in CRM includes many built-in fields that count against this field limit. These include all fields needed for two sets of addresses (46 fields), communication preferences (7 fields), account aging (6 fields) and many more. It’s easy to see how the addition of numerous custom fields to the many built-in fields could cause a problem.
It was up to our CRM experts to identify and implement a solution! We began with a broad discovery – what does the business do and what do they need to track. As our discovery continued, we determined that the recommended solution would be to create multiple custom entities. This enabled us to add as many fields as they needed, keep the fields organized in logical categories, and also prevent any one entity form from being unmanageable.
If you are interested in learning more about our CRM consulting services, contact us via our website or call 205-408-9991. As experts in mobility solutions as well as Microsoft Dynamics CRM, we understand your challenges and can suggest practical solutions. We will help you achieve your strategic objectives faster…and may even help you add a few more achievements to the list.
2B Solutions, Inc. specializes in Microsoft Dynamics Customer Relationship Management (CRM), iOS development, and mobile applications that give organizations the ability to respond to their customers and critical events from anywhere. Dynamics CRM offerings include deployment and customizations for businesses of all sizes in industries of finance, health services, education, retail, distribution, warehousing, government and more. 2B Solutions is a certified Microsoft Partner and certified Apple Consultant.
Max Field Limit Dilemma in Dynamics CRM is a post from: CRM Software Blog
Related posts:
Using a Lookup Entity in CRM 2011 to handle default values and field lengths on a form
Field Trip: Supporting Field Sales Success With Dynamics CRM
Microsoft Dynamics CRM Ease of Use Demonstrated with Changing a Form to Read-Only Based on a Field Value: Part II