Design Question - Managing a Large Number of Account Types RRS feed

  • Question

  • Our organization has 10+ examples of "Account Types": financial institutions, applicants, schools, etc. Each account type will contain unique attributes about that type, and have different relationships to other entities, depending on which account type it is. My question is, what would be the best design approach to represent each of these account types in Dynamics CRM? 

    1. We could try to consolidate everything in the Account entity. One advantage is we'd benefit from all the fields, relationships and functionality that comes with this entity. The downside is we would need to do a lot of maintenance to show/hide information based on the type. Another downside is we would be bombarding this entity with a ton of attributes per type. If each type had 20 unique attributes, we would be creating over 200 columns to maintain this. 

    2. Create individual entity per account type.

    3. Another option, which I may not have thought of. 

    Any thoughts?


    Tuesday, November 24, 2015 7:35 PM

All replies

  • Creating 200 field in an entity is safe as I have created more than 500 fields in an entity in CRM 4. You can show/hide field of Account based on account type using businessrules.

    Another apporoch would be add another entity and show hide fields on that entity based on account type. This is the same work which you have to do but on another entity therefore won't be beneficial. This solution will also work however it will require more energies and will be complicated for user.

    Regards Faisal

    Thursday, November 26, 2015 4:20 PM
  • Apart from Faisal's suggestion you can also consider different form. you can write javascript on load of form and on change of type to switch to different form. 
    Monday, November 30, 2015 1:28 PM
  • In most cases the advantages of using the account entity outweigh the disadvantages. However, there are some SQL limits that you might reach if the fields are mostly boolean, option set or lookups. You start hitting these limits at just over 200 fields of these types. So, if most of your 200 custom fields are of these types, you may cause yourself problems in adding more fields in future. The limits appear as you create the fields, so you could try adding fields in a test environment to see where the limit is (it varies by entity, as it depends on what system fields there already are)

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Monday, November 30, 2015 2:11 PM