CRM MVP Mitch Milam returns as our guest blogger today. You can read more from Mitch at his blog.
The Settings area of CRM 4.0, where many administrators and customizers spend much of their time, can be customized to allow areas to be grouped by functionality. I find this customization allows me to access specific features more quickly than the basic installation – especially when you have a number of custom entities added to the Settings area.
This is the default Settings area display on a system with a single custom entity:
Here is one possible configuration that groups Settings by function:
So how do we make this happen? By modifying the SiteMap, of course, using the following steps:
1) Export the SiteMap and load it into Visual Studio.
2) Scroll down to the bottom of the file and locate the Settings area.
3) We need to make a small addition to the Settings area. Add the ShowGroups attribute as shown below:
1: <Area2: Id=“Settings”3: ResourceId=“Area_Settings”4: Icon=“/_imgs/settings_24x24.gif”5: DescriptionResourceId=“Settings_Area_Description”6: ShowGroups=“true” >
This will instruct CRM to show the Titles for the groups that we’ll be adding next.
4) Next we’ll need to break the Settings Subareas into logical Groups, in whatever manner makes sense to you.
As you can see below, we’re adding a Group tag for each of the groupings. In addition, each of the Groups also needs to have a title, which will be displayed to the user.
5) After you have made the changes to the SiteMap, you need to save it to a new file, so that the original is retained. We may need this in case your edits are incorrect.
6) Import the customized SiteMap.
Note: The SiteMap is one of the rare entities that does not need to be published. It is live as soon as the import completes.
7) Refresh your browser.
8) Navigate to your settings area to admire your handiwork.
If something goes horribly wrong and you receive an error when CRM is displayed, navigate to the following URL ( CRM on-premise ):
or ( for CRM Online ):
Re-import either a corrected version of your modified SiteMap or the original version.
That is pretty much it.
Modifying the SiteMap to alter the appearance and navigation is one of the most valuable services you can perform for your users. If you have the time, I would spend some time in the Microsoft Dynamics SDK reading about the various SiteMap components and thing about how an altered navigation scheme might benefit your customer.