To underline certain character of the menu title, we can use the HTML underline tag ( to the website project.
Drag a Site Map Data Source control on to the page and then the menu control and wrap the menu control inside a div tag.
Create an Html Button control dynamically and attach an onclick event to it. A complete list of access key in different browsers is available here.
Listing 7 //create access key button void Create Access Key Button(string ak, string url) The Site Map.
The purpose of the former event is to insert the target attribute value and create access key for the menu item before it is rendered or displayed in a Menu control.
The latter event is to modify the text displayed by the Site Map Path control. Menu Item Data Bound = new Menu Event Handler(Navigation Menu_Menu Item Data Bound); Site Map.
In CRM 2013 the new navigation bar has been a controversial feature, however when it becomes truly annoying is when using it with a sitemap layout that has not been optimised with it, which is common when upgrading CRM 2011 systems – I have seen one that took 15 clicks of the right arrow to get through all the items in the settings area.
In CRM 2011 you could just hit refresh however in CRM 2013 this can mess up the trail of iframes, breaking the back functionality.
Simple enough, but the control does not provide access key and target window support on menu item. Putting everything together First, add a Site Map to the website project.
Open the web.sitemap file and populate it with your navigation data and structures.
Instead we can combine the code for the previous bookmarklet with the supported code to refresh data on a form.
This will refresh the data on the form without reloading the form itself, preserving the navigation information and is quicker than having the whole page reload.