The issue
You've crafted a beautiful HTML web resource for D365, developed it locally, published into Dataverse via XrmToolbox WebResources Manager plugin, and integrated it seamlessly into your sitemap. Everything works like a charm until you take a look to the browser title.
You just forgot that by default, browser title will match the web resource name, and the web resource name is set automatically by the WebResources Manager equal to the web resource path. Without concerns, you proceed to update the web resource name, publish everything, refresh the browser window and... the browser title keeps clinging to the old name. It's like a ghost from the past haunting your customization.
The solution: a quick sitemap tweak
Here's the swift and effective solution:
- In make.powerapps.com, access the solution containing the sitemap and open the Sitemap Designer.
- Locate the subarea element linked to your HTML web resource.
- Change the "Id" attribute of the subarea element. You can change the whole Id or add an unique suffix, just keep in mind that the Id must be unique among the whole sitemap.
- After making this change, save your sitemap and publish it. This action will force the browser to reload the sitemap definition the next time you access it.
- Reload D365 and access the web resource, the browser title will finally match the new name of your HTML web resource (you may need to hit F5, depending by the browser cache policies).
Conclusions
Customizing D365 with HTML web resources empowers you to tailor your experience. When quirks like outdated browser titles arise, use the sitemap designer to refresh them quickly. Changing the subarea's ID triggers D365 to reload the sitemap, and your browser titles will update. It's a simple yet invaluable trick in your customization toolkit. Happy customizing!