Purpose: To add a Group with SubArea (opening a WebResource), which could be added in a managed solution. Sitemap state before installation and after uninstallation should be same.
I understand how merging in Dynamics works and that is not an issue for me
A generic sitemap inside customizations.xml would look like this
<SiteMap>
<SiteMap IntroducedVersion="7.0.0.0">
<Area Id="MA" ResourceId="Area_Marketing"
DescriptionResourceId="Marketing_Description"
Icon="/_imgs/marketing_24x24.gif"
ShowGroups="true" IntroducedVersion="7.0.0.0">
<Group Id="Test Group" Title="Test Group" IsProfile="false">
<SubArea Icon="$webresource:te_/assets/images/logo.png"
Id="te_survey"
Url="WebResources/te_/index.html"
Title="Test WebResource"
AvailableOffline="true"
PassParams="false"/>
</Group>
</Area>
</SiteMap>
</SiteMap>
However, when I used this I do not see any entry in SiteMap.
I found a post that address my concern directly. It asks to use solutionaction attribute in SubArea/Group elements which let CRM merge sitemap durin installation and uninstallation for a managed solution.
Sadly this does not work in Dynamics365. I lost my whole sitemap when I tried using it.
I think this is a relatively popular scenario.
PS:
I am on Dynamics365 (v8.2), so I cannot hack into the code behind, nor would I prefer it.
I tried How do I remove Dynamics CRM sitemap customizations? , but it does not work in Dynamics365
te_survey
? – Mogilev