Summary: Ms Dynamics Crm 2011 Menus and Ribbon Customizations online free tutorials,materials.
Menus and Ribbon Customizations:
Menus are the options you can see in the File tab of the ribbon, the one that is colored in blue. From that tab you will have a menu, such as Save, New Activity, New Record, Tools,and Options. Notice that every entity has its own menu items as well when you go to create or update a record.Ribbons are the buttons shown in the top bar below the menu. These buttons vary depending on the entity you are positioned on. Examples of these controls are New, Edit,and Export to Excel.
You can customize menus and controls in three ways:
1.Site Map
2.ISV.Config
3.Ribbons
Each way requires a little knowledge of how to manage XML files because they are XML files. When working with XML files, remember the following rules:
1.XML files are case-sensitive, so be sure to respect each node name case to avoid problems. This means that the node name <root> is not the same as <ROOT>.
2.Each node needs to be closed. For example, if you open a node with <root>, you need to later close it with </root>. If the node doesn’t contain children nodes, you can open and close it in the same line—for example, <root />.
Site Map:
The site map is the file that describes the items that will be shown on each area. For example, when you are in the workplace area, you can see on the left the site map options of Dashboard, Activities, Calendar, Imports, and so on. These options are quick links to the entities’ administration that you can customize when you want to have another frequently used entity.
The site map is an XML file that needs to be exported first to be edited, and then it needs to be reimported to be updated. It is recommended to create a new custom solution with only the sitemap extension in order to update the site map quickly. Go to Settings,Solutions, New, and select the view Client Extensions, as shown in Figure 23.22.
FIGURE 23.22 Locating the site map customization by using the Client Extensions view.
The following code illustrates the site map main nodes structure:
<SiteMap>
<SiteMap>
<Area>
<Group>
<SubArea>
Site Map Node:
This is the main and root entry-level node. Inside this node should be another node with the same name, SiteMap, which will contain all the Area nodes as children.
Area Node:
Each area represents the main navigation buttons located on the near navigation that are displayed on the main interface. By default, the Site Map is configured with six main areas:
Figure 23.23 illustrates these navigation options or areas on the Web Application user interface.
The following code illustrates the area node with its default attributes for the Workplace area:
<Area Id=”Workplace” ResourceId=”Area_Workplace” ShowGroups=”true”
Icon=”/_imgs/workplace_24x24.gif” DescriptionResourceId=”Workplace_Description”>
FIGURE 23.23 Areas displayed in the bottom-left corner of the screen.
These are the attributes of the Workplace area code:
Group Node:
This element is used to contain a group of subarea nodes. Each group will be displayed on the near navigation above the Area buttons with the ability to be collapsed or expanded.Samples of groups are My Work and Customers that are included by default in the Workplace area.
Subarea Node:
These nodes are used to provide the links to the pages or websites (configured by its URL) inside the Group sections.For example, suppose we want to add a new area to the sitemap called Webfortis to be used as a collection of links related to our organization and external application. We could add the following code into the Site Map file right after the last </Area> node and before
the </SiteMap>.
<Area Id=”WebfortisArea” Title=”Webfortis” ShowGroups=”true”
Icon=”/_imgs/resourcecenter_24x24.gif” >
<Group Id=”Group1” Title=”External” >
<SubArea Id=”nav_subArea1” Title=”Website”
Icon=”/_imgs/ico_18_129.gif” Url=”http://www.webfortis.com” />
<SubArea Id=”nav_subArea2” Title=”Microsoft”
Icon=”/_imgs/ico_16_sales.gif” Url=”http://www.microsoft.com”
AvailableOffline=”false” />
</Group>
<Group Id=”Group2” Title=”Internal”>
<SubArea Id=”nav_subArea11” Title=”Intranet”
Icon=”/_imgs/ico_18_129.gif” Url=”http://www.webfortis.com/Internal”
AvailableOffline=”false” />
<SubArea Id=”nav_subArea12” Title=”Cost Control”
Icon=”/_imgs/ico_16_sales.gif” Url=”http://www.webfortis.com/CC”
AvailableOffline=”false” />
</Group>
</Area>
Save the changes and import the solution that contains the site map. To import the site map customizations, go to Settings, Solutions, Import, upload the XML file you edited and click the Import Selected Customizations button.
For More Tutorials Click Here
Menus and Ribbon Customizations:
Menus are the options you can see in the File tab of the ribbon, the one that is colored in blue. From that tab you will have a menu, such as Save, New Activity, New Record, Tools,and Options. Notice that every entity has its own menu items as well when you go to create or update a record.Ribbons are the buttons shown in the top bar below the menu. These buttons vary depending on the entity you are positioned on. Examples of these controls are New, Edit,and Export to Excel.
You can customize menus and controls in three ways:
1.Site Map
2.ISV.Config
3.Ribbons
Each way requires a little knowledge of how to manage XML files because they are XML files. When working with XML files, remember the following rules:
1.XML files are case-sensitive, so be sure to respect each node name case to avoid problems. This means that the node name <root> is not the same as <ROOT>.
2.Each node needs to be closed. For example, if you open a node with <root>, you need to later close it with </root>. If the node doesn’t contain children nodes, you can open and close it in the same line—for example, <root />.
Site Map:
The site map is the file that describes the items that will be shown on each area. For example, when you are in the workplace area, you can see on the left the site map options of Dashboard, Activities, Calendar, Imports, and so on. These options are quick links to the entities’ administration that you can customize when you want to have another frequently used entity.
The site map is an XML file that needs to be exported first to be edited, and then it needs to be reimported to be updated. It is recommended to create a new custom solution with only the sitemap extension in order to update the site map quickly. Go to Settings,Solutions, New, and select the view Client Extensions, as shown in Figure 23.22.
The following code illustrates the site map main nodes structure:
<SiteMap>
<SiteMap>
<Area>
<Group>
<SubArea>
Site Map Node:
This is the main and root entry-level node. Inside this node should be another node with the same name, SiteMap, which will contain all the Area nodes as children.
Area Node:
Each area represents the main navigation buttons located on the near navigation that are displayed on the main interface. By default, the Site Map is configured with six main areas:
- Workplace
- Sales
- Marketing
- Service
- Settings
- Resource center
Figure 23.23 illustrates these navigation options or areas on the Web Application user interface.
The following code illustrates the area node with its default attributes for the Workplace area:
<Area Id=”Workplace” ResourceId=”Area_Workplace” ShowGroups=”true”
Icon=”/_imgs/workplace_24x24.gif” DescriptionResourceId=”Workplace_Description”>
These are the attributes of the Workplace area code:
- Id—The unique identifier name for each area.
- ResourceId—The ResourceId.
- ShowGroups—This attribute is necessary only if the area has more than one Group child node.
- Icon—The URL for the icon to be displayed near the Area title.
- DescriptionResourceId —This is for internal use only.
Group Node:
This element is used to contain a group of subarea nodes. Each group will be displayed on the near navigation above the Area buttons with the ability to be collapsed or expanded.Samples of groups are My Work and Customers that are included by default in the Workplace area.
Subarea Node:
These nodes are used to provide the links to the pages or websites (configured by its URL) inside the Group sections.For example, suppose we want to add a new area to the sitemap called Webfortis to be used as a collection of links related to our organization and external application. We could add the following code into the Site Map file right after the last </Area> node and before
the </SiteMap>.
<Area Id=”WebfortisArea” Title=”Webfortis” ShowGroups=”true”
Icon=”/_imgs/resourcecenter_24x24.gif” >
<Group Id=”Group1” Title=”External” >
<SubArea Id=”nav_subArea1” Title=”Website”
Icon=”/_imgs/ico_18_129.gif” Url=”http://www.webfortis.com” />
<SubArea Id=”nav_subArea2” Title=”Microsoft”
Icon=”/_imgs/ico_16_sales.gif” Url=”http://www.microsoft.com”
AvailableOffline=”false” />
</Group>
<Group Id=”Group2” Title=”Internal”>
<SubArea Id=”nav_subArea11” Title=”Intranet”
Icon=”/_imgs/ico_18_129.gif” Url=”http://www.webfortis.com/Internal”
AvailableOffline=”false” />
<SubArea Id=”nav_subArea12” Title=”Cost Control”
Icon=”/_imgs/ico_16_sales.gif” Url=”http://www.webfortis.com/CC”
AvailableOffline=”false” />
</Group>
</Area>
Save the changes and import the solution that contains the site map. To import the site map customizations, go to Settings, Solutions, Import, upload the XML file you edited and click the Import Selected Customizations button.
For More Tutorials Click Here
0 comments:
Post a Comment