none
Removing redundant entity attributes

    Question

  • I am planning on undertaking optimisation and maintenance works on our CRM system.

    We have accrued custom attributes in the Contact entity that are no longer in use, what would be the best approach to removing these?

    Our environment: Windows 2008 Svr, SQL Svr 2008, Dynamic CRM 4 Rollup 10, Outlook client.

    Thanks in advance.

    Friday, December 10, 2010 12:30 PM

Answers

  • Please also keep in mind that there are already a number of standard attributes against the Contact entity.

    I suggest that you first determine and/or evaluate which "redundant" fields on the Contact entity are custom + don't contain historical details + wouldn't be of any use in the future (some of the standard fields may be re-usable).

    After this:

    For the fields that contain historical data (custom or standard), remove these off the views and form but do not delete them (also check that there are no JavaScript dependencies on these). I would also add some sort of comment or indicator in the description of the attribute to flag it's "historical" status.

    For the standard fields (which you don't use), I suggest removing them off the views and form and making them not searchable (in the attribute properties) - this will keep them out of the way and eliminate any confusion for users when they are determining criteria while searching.

    For the custom fields which DON'T contain historical data or any dependencies (consider javascript, workflow, plug-ins, custom code) - you may delete these, I would suggest backing up customizations first to be on the safe side.

    Thanks,

    Maryse

     


    The xRM Architect:
    Sunday, December 12, 2010 5:40 AM

All replies

  • Remove them from the form and views, publish the entity, delete the attributes, publish the entity. Is this what your looking for?
    MSCRM Bing'd - http://bingsoft.wordpress.com
    Check out the CRM 4 to CRM 2011 JavaScript Converter Tool
    CRM Forum Guidance on how to Help Us Help You
    Friday, December 10, 2010 2:24 PM
    Moderator
  • I presume the fields are no longer used, and that you don't need to see historical data in these fields?

    If you might, then it might be better to move them to another tab and hde it.

    Rob


    www.crmconsult.info Twitter:robertpeledie
    Friday, December 10, 2010 2:33 PM
  • Please also keep in mind that there are already a number of standard attributes against the Contact entity.

    I suggest that you first determine and/or evaluate which "redundant" fields on the Contact entity are custom + don't contain historical details + wouldn't be of any use in the future (some of the standard fields may be re-usable).

    After this:

    For the fields that contain historical data (custom or standard), remove these off the views and form but do not delete them (also check that there are no JavaScript dependencies on these). I would also add some sort of comment or indicator in the description of the attribute to flag it's "historical" status.

    For the standard fields (which you don't use), I suggest removing them off the views and form and making them not searchable (in the attribute properties) - this will keep them out of the way and eliminate any confusion for users when they are determining criteria while searching.

    For the custom fields which DON'T contain historical data or any dependencies (consider javascript, workflow, plug-ins, custom code) - you may delete these, I would suggest backing up customizations first to be on the safe side.

    Thanks,

    Maryse

     


    The xRM Architect:
    Sunday, December 12, 2010 5:40 AM
  • Thank you for taking the time to respond from what seems to be a very vague query – apologies. You’ll be pleased to know that your assumptions are correct and Maryse answer is  what I’m looking for.

    Tuesday, December 21, 2010 11:23 AM