The Site Map Designer is a visual way to update your sitemap for your app. The Site Map Designer allows you to update the default site map (which was the site map we’ve known and loved over the years for past versions of CRM), as well as app specific site maps.
This means that now you could have more than one site map in your deployment depending on how many apps you have. If you don’t have any apps, then you’ll have the single “Site Map” under Site Map components. However, if you have at least one app, when you go to add a Site Map to your solution, you’ll see the default/base site map, as well as your app specific site maps.
Launching the Site Map Designer
To kick off the Site Map designer from your app, simply click the arrow pointing up to the right on the Site Map area of the app designer. You can also kick it off by double clicking on the specific Site Map component in your solution, but depending on the XML in the Site Map, the designer may not be able to load it (see below).
You’ll be presented with a blank canvas with a default Area and Subarea already placed on the canvas for you. You simply need to rename these using the Titles and Descriptions area, as well as update the ID, Icon, Show Groups, and URL (more details below about each site map components properties that can be edited).
In the Site Map designer, you can click the + icon in the top right corner to add a new component to your site map, or you can drag / drop the component from the right side over to the canvas to add it to your site map.
The table below shows the components that can be added onto the canvas, along with the properties per component that can be configured.
Show Groups (flag)
Set as Profile
|Sub Area||Type (Dashboard, Entity, Web Resource, URL) |
Privileges (Entity, then All/Create/Read/Write/Delete/Append/AppendTo/Share/Assign)
SKUs (All, OnPremise, SPLA, Live)
Client (All, Outlook, Web, Outlook Laptop Client, Outlook Workstation Client)
If you add an entity to the Site Map that’s not a part of your App artifacts yet, it’ll automatically get added to your App without any forms, views, or charts selected for filtering.
Note that some of the Sub Area options become read only based on the type you select. For example, if you don’t select Entity as the type, then the Entity dropdown that allows you to select the entity is read only as it only applies to that type of component.
If you wanted to, you can still export the app specific site map, and mess with the XML directly (if you’re courageous). However, if you do so, be careful because some of the preexisting site map XML is not supported in the site map designer. For example, I stole the “Settings” and “Training” areas of the main site map for my custom app specific site map, and had to comment out the following in my app specific site map because the designer wouldn’t load with it included.
<!--SubArea Id="nav_plugintrace" ResourceId="Homepage_PluginTraceLog" Icon="/_imgs/area/Plugin_TraceLog_32.png" Entity="plugintracelog" Client="Web" IntroducedVersion="220.127.116.11">
<Privilege Entity="plugintracelog" Privilege="Read" />
<!--SubArea Id="nav_systemjobs" ResourceId="Homepage_SystemJobs" DescriptionResourceId="SystemJobs_SubArea_Description" ToolTipResourseId="SystemJobs_SubArea_ToolTip" Entity="asyncoperation" Url="/tools/business/home_asyncoperation.aspx" AvailableOffline="false" IntroducedVersion="18.104.22.168" /-->
<!--Privilege Privilege="LearningPath" /—>
Until I commented those out, I would receive an error such as the following when I tried to go back into the Site Map designer.
However, after I removed all the unsupported XML, I was then able to go into the Site Map designer and see all the Settings and Trainings components in my site map and I had the ability to tweak them using the new Site Map designer way, versus the old manual XML updates way.