Simplify Navigation: Building and Managing SiteMaps in Microsoft Dynamics CRM 2011

SiteMap Editor for Microsoft Dynamics CRM 2011 — Tips to Customize Navigation Fast

What it is

The SiteMap Editor is a tool (often a third-party XrmToolBox plugin or a standalone editor) that lets you visually edit the CRM sitemap XML used by Dynamics CRM 2011 to control the application navigation: areas, groups, and subareas (entities, dashboards, URLs, web resources).

Why use it

  • Edit navigation visually instead of hand-editing XML.
  • Reorganize areas and groups quickly.
  • Add or hide entities, dashboards, and external links.
  • Create role-based navigation by adjusting the Privilege and IsVisible attributes.

Quick tips to customize navigation fast

  1. Work on a copy
    Export your solution or save the current sitemap XML before changes so you can roll back.

  2. Use a visual SiteMap tool
    Install a trusted SiteMap Editor (e.g., XrmToolBox SiteMap Editor plugin) to drag-and-drop areas/groups and preview structure.

  3. Plan navigation by user role
    Map primary user tasks to top-level Areas. Keep each Area focused (Sales, Service, Marketing, Admin) so users find what they need quickly.

  4. Minimize top-level items
    Keep Areas to a small set (4–6). Put related items in Groups and Subareas to reduce clutter.

  5. Set appropriate Privileges
    Use the Privilege or display rules to show items only to users with relevant security roles. Prefer role-based visibility over hiding with IsVisible when possible.

  6. Use Subareas smartly

    • Use entity subareas for record lists/forms.
    • Use URL/web resource subareas for dashboards, external apps, or quick links.
    • Set the Icon and Title labels to be short and recognizable.
  7. Optimize labels and icons
    Short, clear labels and distinct icons speed recognition. Use existing resource labels where possible to support localization.

  8. Group related functions
    Put related subareas (e.g., Leads, Opportunities, Quotes) together under a single Group to reduce navigation jumps.

  9. Test with real users
    After changes, have representative users verify the flow and accessibility on both web and mobile clients.

  10. Deploy via solution for controlled rollout
    Import the edited sitemap into a managed/unmanaged solution to deploy across environments and maintain versioning.

Common pitfalls to avoid

  • Editing production sitemap without backup.
  • Creating too many top-level Areas.
  • Relying solely on IsVisible without proper security role checks.
  • Forgetting to update localized labels for non-English users.

If you want, I can:

  • provide step-by-step instructions for using the XrmToolBox SiteMap Editor; or
  • generate a sample sitemap XML snippet for adding an Area/Group/Subarea.

Comments

Leave a Reply

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