Application navigation Configuration

Application navigation Configuration

Microsoft Dynamics CRM 4.0 between des a navigation model that lets you
Integrate other Web applications or modify the default navigation. This is
Called the sitemap.

With the sitemap, you can control the navigation structure and precise
Placement and order of sub areas within the application navigation structure.

 

Sitemap Overview

Sitemap Overview

You can add custom entities into the navigation structure by using
Customize entitiesArea in the application by selecting
Areas that display this entityOn the General tab for the entity.
However, this does not let you control the precise placement within the area.
For example, by using the mizmization tools, you cannot control the order that
The new entity will appear under sales. An example of the navigation structure
Is shown in the following diagrams.

The application navigation is created as an in-memory representation of
Sitemap by combining the three data sources shown in the following diwing.

The user interface for the Microsoft Dynamics CRM application is constructed
From the following elements:

• The sitemapxml
  Attribute of the organization entity.
• Client extension controls configured using isV. config.
• Custom entity information that is contained in the metadata database.

NoteThe additions to the application navigation
Structure described in the Entity metadata is automatically appended to the end
Of the appropriate areas defined in the sitemap XML reference. These
Additions lack the precise control of placement.

You can accessSitemapxmlAttribute by exporting the sitemap.
After you configure this XML file, you must import it to apply
Customizations.

The sitemap defines the areas represented in the Web Client's Navigation Pane
As well as in Microsoft Dynamics CRM for Microsoft Office outlook.

Sitemap also defines workplace profiles. These are groups of subareas that
End-users can add or remove from the workplace area by using the user settings
For workplace. The go to menu and user settings for the start page (Web Client
Only) automatically reflect the navigation areas and subareas defined in
Site map.

The site map does not provide configuration support for the entity form left
Navigation Pane, nor does it make the functionality in isV. config obsolete.
Continue to use isV. config to add such items as menus and buttons to
Application and navigation areas to entity forms.

The site map can be exported and imported to move your customizations
Development and production environments.

Workplace profiles

The workplace is a user-defined able area that lets the user select from
Set of profiles defined in the site map. These profiles typically will be
Configured to contain the most frequently used areas of the application. This
Enables users to create a workspace that is customized for their job
Responsibilities.

There are two groups that are always shown in the workplace:My work
AndMERs. These contain the pages of the application that are
Typically used by all users of the system. Technically, these are not profiles.
For more information, see sitemap
XML and sitemap schema.

The user can decide to add groups by selecting from a list of profiles in
UsingPersonalize workplace...Area of the workplace.
Default profiles include the following:

• Sales
• Marketing
• Service
• Scheduling

These groups and profiles are customizable by using the site map. You can
Add, remove, modify, and rename profiles to best meet the needs of
Users.

Microsoft Dynamics CRM for outlook

The areas, workplace groups, and subareas defined in the site map are
Reflected in the outlook folder hierarchy under the Microsoft Dynamics CRM
Folder. However, Microsoft Dynamics CRM for Microsoft Office outlook represents
The folders alphabetically. The order defined in the site map does not
Apply.

Example scenarios

The following list contains examples of what you can do with the site map:

• Integrate other applications into the Microsoft Dynamics CRM application.
• Customize workplace profiles to better match with user responsibilities.
• Add M entities in the navigation where you want them.
• Remove an unused top level area.
• Add a new top level area.

 

See also

Concepts

• Adding Client
  Extension controls
• Editing the sitemap
• Passing parameters to
  URL using sitemap

Reference

• Sitemap XML reference

Other resources

• Application
  Navigation Configuration

Editing the sitemap

Editing
Sitemap

To configure the sitemap, do the following:

1. Export the sitemap by using the Export mizmizations feature.
   1. In the Navigation Pane, clickSettings, Click
      Customization, And then clickExport mizmizations.
   2. SelectSitemap, Then onActionsToolbar click
      Export selected mizmizations.
2. Create a backup copy of the exported customizations.zip file. Use this file
   To recover from errors if necessary.
3. Extract the customizations. xml file from the customizations.zip file.
4. Make your changes to the exported XML file.
5. Import the updated XML file by using the import customizations feature.
   1. In the Navigation Pane, clickSettings, ClickCustomization,
      And then clickImport mizmizations.
   2. ClickBrowse, Locate your modified XML file, and then click
      Upload.
   3. On the actions toolbar, clickImport selected mizmizations.

Recovering from errors

The import tool performs Validations on the sitemap. However, it is still
Possible that some errors might occur.

If errors occur, the default sitemap will be applied and an error message
Will be displayed. You must fix the errors in the sitemap and import it
Again.

 

Passing parameters to a URL using sitemap

Passing
Parameters to a URL using sitemap

Passing parameters to the target URL for a subarea element in sitemap is a way
Provide the target application with information about the organization and
Language Context of the user and the Organization. All the parameters are passed
IfSubareaElement is configured by usingPassparams
Attribute.

You can indicate whetherSubareaPasses the following
Parameters:

Parameter	Name	Description
Orgname	Organization Name	The unique name of the organization.
Userlcid	User language code	Represents the language code identifier that is used by Current user.
Orglcid	Organization language code	The language code identifier representing the base language The organization.

Language codes are a four digit locale ID. Valid locale ID values can be
Found at msdn2.microsoft.com/en-us/library/0h88fahh.aspx

Example

Without parameters:

http://myserver/mypage.aspx

With parameters:

http://myserver/mypage.aspx?orgname=AdventureWorksCycle&userlcid=1033&orglcid=1033

Reading passed parameters

Passed parameters are usually read in the target. ASPX page by using
Httprequest. querystringProperty. For more information, see:
Msdn2.microsoft.com/en-us/library/system.web.httprequest.querystring.aspx.