Lately I have had several occasions where deleting or importing a managed solution has removed groups and their subareas from the Microsoft Dynamics 365 Customer Experience (from here on out known as CRM) sitemap. The sitemap is the area at the top of CRM used for navigation. The two groups that seem to be affected are under Settings. The Process Center group, which contains the subarea Processes where workflows, business process flows, dialogs, task flows and actions live. The other group getting the smack down is Applications where the subarea My Apps typically hang out.
I have seen this happen most often when importing the Organizational Insights solution. Of course now Organizational Insights is available outside of the application in the Admin Center as a preview so it should not be removing stuff anymore. Now don’t get me wrong, Organizational Insights is is a great tool. It allows you to see metrics on things like adoption, storage, performance and even helps with troubleshoot failing workflows and API calls. We have started using this solution with a couple of our clients and every time I installed it, the Process Center group and Applications group would disappear from under the Settings area. And I did not notice at first. I had one of those "isn't Processes supposed to be here???" moments. Since I did not see the issue right away it took me a bit to figure out what had happened. I simply added the missing groups back. It was not until I had the occasion to install the solution and then go right to Processes that I realized what was happening.
Although there are a couple of ways to fix this I recommend using the Sitemap Designer you can access right within CRM. In order to do this you need to create a solution.
I always recommend creating solutions when making changes to CRM. Two reasons, first best practices means when changes are made they are first made in a test environment and then moved to production after proper testing. Second, if that is not the way you roll or you only have one environment, solutions are still a good idea because you can use them to track the changes you make. Especially now that you can get granular with them. Not like the olden days when you had to move the whole entity... the horror! So lets number this out.
If other things disappear you can use this same process to add them back. Now of course you could solve this by moving the sitemap from another environment but then whatever you imported would not be there so you would have to add that back. If that is the way you go, Add your sitemap to a solution and gather the information you need to add back the stuff that will be missing when you import a sitemap from another org.
Need a team to help you work through scenarios just like this one? Contact us for more information about ongoing support!
So hopefully these step will help you get back what was lost. Enjoy! And I hope you are having a lovely day wherever you are.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.