I was recently assisting a customer with an import of their CRM 2011 organization into a new CRM 2013 deployment. The import completed successfully and after logging in we noticed that the some of the sitemap links were either broken (no response when clicking on them) or completely missing when compared with a brand new CRM 2013 organization.
Examples of Missing Links:
Examples of what might be missing:
We were able to restore the missing links and fix the broken links by using the SiteMap Editor from the XRM ToolBox. The sitemap links in question were all out of the box and the customer had only added a few customized links within the SubArea element of the sitemap. The steps for resetting your sitemap to the 2013 defaults are outlined below. Please read the disclaimer below before following these steps.
Disclaimer: The steps below will reset the top 3 elements of your CRM sitemap. If you have added custom sitemap links in the Area>Group>SubArea elements of your sitemap, these changes will be overwritten with the default sitemap values. There is a step below outlining how to backup your pre-existing sitemap in case you do need to perform a restore, but it is not advised to move forward with these steps unless you plan to add back those custom sitemap links manually. As an alternative solution, review the information at the following link to add the new sitemap areas manually after upgrading your organization: http://msdn.microsoft.com/en-us/library/dn486920.aspx
Steps for Resetting your 2013 SiteMap to the Default Values
1. Download the XRM Toolbox for Dynamics CRM 2011/2013 found at: http://xrmtoolbox.codeplex.com/
2. Once downloaded, extract the package contents
3. Open File Explorer and browse to the location where you extracted the package
4. Locate the XrmToolBox.exe file, right-click on the file and click Run as administrator Note: If your receive an error stating you must first install .NET 4.0, please download and install before continuing to the next step.
5. Once the application is open, click on the Connect to CRM icon in the upper left-hand corner
6. On the Select connection page, click New Connection
7. Enter the connection information for your CRM deployment and click Get Orgs to populate the Organization dropdown box
8. Select the Organization that contains the broken sitemap from the Organization dropdown box and click OK
9. Click Yes to confirm you’d like to connect now
10. You should now see your connection listed in the lower-left corner of the ToolBox window
11. On the ToolBox main menu, scroll down the list of tools and click on SiteMap Editor
12. On the SiteMap Editor tab, click Load SiteMap
You should now see the sitemap listed in the SiteMap dialogue box on the left
13. From the actions menu, click Save SiteMap to export a copy of the pre-existing sitemap for backup purposes
14. Click OK to the SiteMap Saved informational message
15. Now that you have a backup of your sitemap, click the More actions dropdown and click Reset CRM 2013 SiteMap to default
16. Click Yes when asked if you are sure you want to reset the sitemap
17. Click Update SiteMap to apply the changes
18. You should now be able to login to CRM and verify that your sitemap is fully functional
If you have any additional SiteMap tips or tricks you'd like to share with the community, please comment below!
Thanks! Reed Wolfe Premier Field Engineer
Perfect timing! Just had a customer ask about this.
Thank you for using and demonstrating my toolbox.
You just missed one step. At the end, you have to click on button "update sitemap" so the change takes effect
The missing step has been added, thank you Tanguy. Thanks for such a great tool!
For us, the upgrade for Sping '14 reset our sitemap to default which has the first three you are showing. I have to use the tool to set our map back to the way it was.
Thank you though for posting this it is perfect timing!
Hi 2tim24u, thanks for sharing and glad this post was able to help you out!
This is AWESOME!!! Great post.
Great Article Reed!!!!!!!!!!!!
Should have done better googling - arrived at the same solution after some ranting - great post!