Tip #225: When CRM makes ye say “Arrrrrrgh!”

Friday, September 19
International Talk Like a Pirate Day 2014

If ye be usin’ Dynamics C Arrrrrrrrrrrr M fer several years, ye may spy wit’ ye eye that CRM starts runnin’ like a scallywag. Here be several thin’s ye can do to swab th’ deck ‘o ye CRM system, hoist performance, ‘n spit shine th’ cobwebs out ‘o th’ cornerrrs. Trrrrranslate, arrrrrrgh! Trrrrranslate, arrrrrrgh!

If you have been using Dynamics CRM for years, you may have noticed that the system has started to run a bit slower. Here are a few things that you can do to clean up your CRM system, improve performance, and cut some of the clutter that may have started to build up.

  1. Careen asynchronous table, ‘n if ye don’t already, schedule bulk scuttle jobs t’ do it magically. Trrrrranslate, arrrrrrgh!

    Clean up asynchronous table, and if you don’t already, schedule bulk delete jobs to do it automatically

  2. Hoist th’ newest update rollup. Trrrrranslate, arrrrrrgh!

    Deploy latest update rollup

  3. Swab th’ POA table. Use Buccaneer Sewell’€™s secret decoder rin’. Trrrrranslate, arrrrrrgh!

    Clean up the POA table. Use Scott Sewell’s secret decoder ring.

  4. Make sure ya ‘ave a good stash strategy. Trrrrranslate, arrrrrrgh!

    Review backup strategy.

  5. Refresh dev/QA orgs. Make th’ existin’ orgs walk the plank, import updated copy o’ production MSCRM database. Trrrrranslate, arrrrrrgh!

    Refresh dev/QA orgs. Drop the existing organizations, import updated copy of production MSCRM organization.

  6. Use th’ CRM data detective t’ review how frequently fields be populated. Delete/hide unused fields ‘n entities. All mateys have those “’twas a good ideas but avast, didn’t pan out”€ type entities in their crew. If ye ‘ave any o’ these or any fields that were added ‘n then nah used, scuttlin’ these can ‘ave a big bounty. Trrrrranslate, arrrrrrgh!

    Use the CRM data detective to review how frequently fields are populated. Delete/hide unused fields and entities. Everybody has those “good ideas that didn’t pan out” type entities. If you have any of these or any fields that were added and then not used, deleting these can have a big benefit.

  7. Look at rigs to stop plundering. If ye ‘ave added entities o’er time, chances are that th’ roles don’t reflect yer original security strategy. Maybe good time t’ switch t’ a base security role stratarrrrgy. Trrrrranslate, arrrrrrgh!

    Review security roles. If you have added entities over time, chances are that the roles don’t reflect your original security strategy. Maybe good time to switch to a base security role strategy.

  8. Review audit settin’s/duplicate detection settin’s to verify they be set correctly. These thin’s get turned off when solutions be imported. Chances be that some ‘o them be disabled. Trrrrranslate, arrrrrrgh!

    Review audit settings/duplicate detection settings to verify they are set correctly. These things get turned off when solutions are imported. Chances are that some of them are disabled.

  9. Review searchable field settin’s usin’ th’ xrm toolbox. Set fields not used on forms (other than system required fields) to be non searchable ‘n simplify Advanced Find. Trrrrranslate, arrrrrrgh!

    Review searchable field settings using the xrm toolbox. Set fields not used or on forms (other than system required fields) to be non searchable and simplify Advanced Find.

  10. Pillage any junk views ‘n reports. I define “junk” as views ‘n reports that be not actively used by anyone. Trrrrranslate, arrrrrrgh!

    Remove any junk views and reports. I define “junk” as views and reports that are not actively used by anyone.

  11. Organize ye olde trreasurremap. Frequently a crew that be in place fer several years gets a lot ‘o junk in th’ sitemap, like a settin’s area wit’ 75 links. I like to cut out anythin’ that does not have to be in th’ settin’s area. Fer thin’s like lookup entities fer country that never change, I like to remove from settin’s area fer simplification. If someone needs to modify ’tis list, they can do it via advanced find. Trrrrranslate, arrrrrrgh!

    Organize your sitemap. Frequently a deployment that has been in place for several years gets a lot of junk in the sitemap, like a settings area with 75 links. I like to cut out anything that does not have to be in the settings area. For things like lookup entities for country that never change, I like to remove from settings area for simplification. If someone needs to modify this list, they can do it via advanced find.

  12. Remove any third parrrty add-ons that be no longer used. Again, that fax integration was a jolly idea at th’ the hour, but do we really still need it? Trrrrranslate, arrrrrrgh!

    Remove any third party add-ons that are no longer used. Again, that fax integration was a good idea at the time, but do we really still need it?

  13. Upgrade to CRM 2013 SP1. Or if ye are not prepared to release the kraken, at least upgrade components like SQL Serrrrver ‘n Internet Pirate to newer versions to make yon future upgrades easier. Trrrrranslate, arrrrrrgh!

    Upgrade to CRM 2013 SP1. Or if you aren’t ready to upgrade, at least upgrade components like SQL Server, Internet Explorer to newer versions to make future upgrades easier.

Leave a Reply

Your email address will not be published. Required fields are marked *