Add Language Localization to InfoPath 2007 Form

When a form is used in several different countries the need for easy language localization becomes a very necessary goal. By leveraging expression boxes, a secondary data source, and data filtering techniques the ability to easily switch between languages on a form becomes a small feat.

Figure 1. An example of an InfoPath Form with localized text.
Although changing labels in a form is not difficult, there are will be some aspects missing from the form that keep it from achieving true localization. The following are some areas where you might run into problems when internationalizing your form:

• Tooltip text
• Insert Item links for repeating tables and sections
• Button labels
• Calendars from different parts of the world

In this task we will create a new blank form with a connection to a secondary data source that provides language localization settings. Let’s start by creating the XML file that will store the language settings.
Create the secondary data source:
Copy the following code into a text editor, and then save the file as Language Settings.xml:

<?xml version="1.0" encoding="UTF-8"?> <LocalSettings>     <Languages>         <Language Name="English" Code="ENG"/>         <Language Name="Español" Code="SPA"/>         <Language Name="Français" Code="FRE"/>        </Languages>     <Labels>         <Label Name="First Name">             <LocalLabel Code="ENG" Value="First Name"/>             <LocalLabel Code="SPA" Value="Nombre"/>             <LocalLabel Code="FRE" Value="Nom"/>            </Label>         <Label Name="Last Name">             <LocalLabel Code="ENG" Value="Last Name"/>             <LocalLabel Code="SPA" Value="Apellido"/>             <LocalLabel Code="FRE" Value="Nom de Famille"/>            </Label>         <Label Name="Phone Number">             <LocalLabel Code="ENG" Value="Phone Number"/>             <LocalLabel Code="SPA" Value="Número de Teléfono"/>             <LocalLabel Code="FRE" Value="Numéro de Téléphone"/>            </Label>         <Label Name="Address">             <LocalLabel Code="ENG" Value="Address"/>             <LocalLabel Code="SPA" Value="Dirección"/>             <LocalLabel Code="FRE" Value="Adresse"/>                </Label>         <Label Name="Age">             <LocalLabel Code="ENG" Value="Age"/>             <LocalLabel Code="SPA" Value="Edad"/>             <LocalLabel Code="FRE" Value="Age"/>         </Label>         <Label Name="FavoriteColor">             <LocalLabel Code="ENG" Value="Favorite Color"/>             <LocalLabel Code="SPA" Value="Color Favorito"/>             <LocalLabel Code="FRE" Value="Couleur Préférée"/>         </Label>     </Labels>     <Colors>                <LocalColor ID="Blue" Code="ENG" Value="Blue"/>         <LocalColor ID="Blue" Code="SPA" Value="Azul"/>         <LocalColor ID="Blue" Code="FRE" Value="Bleu"/>                <LocalColor ID="Green" Code="ENG" Value="Green"/>         <LocalColor ID="Green" Code="SPA" Value="Verde"/>         <LocalColor ID="Green" Code="FRE" Value="Vert"/>                <LocalColor ID="Red" Code="ENG" Value="Red"/>         <LocalColor ID="Red" Code="SPA" Value="Rojo"/>         <LocalColor ID="Red" Code="FRE" Value="Rouge"/>                <LocalColor ID="Yellow" Code="ENG" Value="Yellow"/>         <LocalColor ID="Yellow" Code="SPA" Value="Amarillo"/>         <LocalColor ID="Yellow" Code="FRE" Value="Jaune"/>            </Colors> </LocalSettings>

Now that we have our secondary data source, let’s design our form.
Add the secondary data source:

1. Design a new blank form.
2. Choose Data Connections from the Tools menu, and then click Add.
3. In the Data Connection Wizard, select Receive Data, and then click Next.
4. Select XML Document, and then click Next.
5. Click Browse, locate and select the Language Settings.xml file, click Open, and then click Next.
6. Click Finish, click Yes, and then click Close.

Add the language selection drop-down list:

1. Open the Controls task pane.
2. Add a drop-down list box to the view.
3. Double-click the new drop-down list, rename the field to LanguageChoice, and then select Look Up Values From A Data Connection in the List Box Entries section.
4. Select Language Settings from the Data Connection drop-down list.
5. Select /LocalSettings/Languages/Language for the Entries field by clicking on the icon to the right of the field.
6. Select @Code for the Value and @Name for the Display Name. Refer to Figure 2.
7. Click OK to close the Drop-Down List Box Properties dialog box.

Figure 2. Configuring the language selection drop-down list.

Add the layout table and controls:

1. Open the Layout task pane.
2. Insert a Custom Table with 3 columns and 4 rows.
3. Merge the last two columns of the third and fourth row (refer to Figure 5).
4. Open the Controls task pane, and then insert a text box control into the first column of the second row.
5. Double-click this text box, change the name to FirstName, and then click OK.
6. Insert a text box into the second column of the second row, and then change the name to LastName.
7. Insert a text box into the last column of the second row, and then change the name to Age.
8. Insert a text box into the first column of the last row, and then change the name to PhoneNumber.
9. Insert a text box into the last column of the last row, and then change the name to Address.

Now that all of the controls are in the layout, we need to add labels so that the user knows what information to type into each field. Using expression boxes we can dynamically set the content of each label depending on the language preference.

LOCALIZED FIELD LABELS
Add the expression boxes with data filtering:

1. Click inside the first column of the first row to set the insertion point.
2. Select Expression Box from the Controls task pane.
3. Click the Function button on the dialog box that appears.
4. Click Insert Field or Group in the Insert Formula dialog box.
5. Select Language Settings (Secondary) from the Data Source drop-down box, select /LocalSettings/Lables/Label/LocalLabel/Value, and then click Filter Data.
6. Click Add.
7. Select Name from the Select A Field or Group first drop-down list, select Labels/Label/Name, click OK, and then type First Name into the third drop-down list.
8. Click And, select Code from the first drop-down list, and then select Select A Field Or Group from the third-drop down list.
9. Select Main from the Data Source drop-down list, and then select myFields/LanguageChoice.
10. Click OK 6 times.
11. Repeat steps 1 through 9 for each additional label, except in step 7 type the text that corresponds to whichever label you are adding.

Figure 3. Specifying the filter conditions.

Figure 4. The completed function for the expression box.

Make the labels bold:

1. Select all of the expression boxes by holding the Ctrl key while clicking each one.
2. Click the Bold button (or type Ctrl+B).

Figure 5. The completed view.

Now our form has labels that change depending on what the user selects from the drop-down list. Let’s preview our accomplishments before adding a finishing touch.
Preview the form:

1. Click Preview Form (or type Alt+P).
2. Select any of the languages from the drop-down list.
3. Notice how the labels are blank originally and then change to the specified language depending on what is chosen from the drop-down list.

Figure 6. Selecting the language.

Figure 7. Labels in Spanish.

To remedy the problem of all of the labels being blank by default we will add a default value to the myFields/LanguageChoice node.

Set the default language:

1. Open the Data Source task pane.
2. Double-click the myFields/LanguageChoice node.
3. Type ENG as the Default Value, and then click OK.

With another quick preview you will see that the drop-down list is automatically set to English and none of the labels are blank.

LOCALIZED DROP-DOWN LISTS
Now that the expression boxes have all been updated to display appropriate labels depending on the language choice, we will add a drop-down list that demonstrates similar functionality. The secondary data source already has elements with all of the correct information, so we will simply add a drop-down list with the appropriate data filtering.
Add the drop-down list:

1. Click below the table to set the insertion point and type Enter a few times to insert some white space.
2. Add an expression box that displays the Favorite Color label using the process described in the first section.
3. Open the Controls task pane and select Drop-Down List to insert a new control.
4. Double-click the drop-down list, and then change the name to FavoriteColor.
5. Select Look Up Values In A Data Connection, select Language Settings from the data source drop-down list, and then click the field selection button.
6. Select Colors/LocalColor, and then click the Filter Data button.
7. Click Add, select Code from the first drop-down list, and then select Select A Field Or Group from the third drop-down list.
8. Choose Main from the data source drop-down list, select /myfields/LanguageChoice, and then click OK four times to return to the Drop-Down List Box Properties dialog box.
9. Select the @ID attribute as the Value for the entries, select the @Value attribute as the Display Name, and then click OK.

LOCALIZED BUTTONS
The last aspect of adding localization to the form will be making sure that the button labels are correctly displayed. Unfortunately, InfoPath does not allow the button labels to be changed programmatically, so we are forced to use several button controls with conditional formatting to solve this problem. This same process can be used to change the tooltip text and Insert Item links for repeating tables and sections, but depending on how many languages need to be supported this can generate tremendous amounts of clutter in design mode.
Add the buttons:

1. Open the Controls task pane and insert a button onto the view.
2. Double-click the button, change the Label to Submit, change the ID to butSubmit.
3. Click the Display tab, click the Conditional Formatting button, and then click Add.
4. In the first drop-down list select LanguageChoice, select Is Not Equal To in the second drop-down list, and then select Type Text and type ENG into the third drop-down list.
5. Select Hide This Control, and then click OK three times.
6. Copy and paste the button until there are three identical buttons right next to each other.
7. Change the Label on the second button to Sométase, change the ID to butSubmit, and then follow step 4 to apply conditional formatting using SPA as the text instead of ENG.
8. Change the Label on the third button to Soumettre, change the ID to butSubmit, and then follow step 4 to apply conditional formatting using FRE as the text instead of ENG.

Note: The ID of all three buttons should be the same because they will all perform the same action and any code that you attach to one button should be attached to the others.

Figure 8. The completed form in design mode.



Source: http://www.infopathdev.com/blogs/matt/archive/2006/02/02/Add-Language-Localization-to-a-Form.aspx

Filtering Lookups in CRM 4

Lets get straight to the solution. Suppose you want to filter the Primary Contact lookup on the Account entity to show only contacts that belong to the data in the Parent Account field. 

Below is a simple JavaScript code to achieve that.

• On the forms OnLoad event write the following code.

/* Form.onLoad() */
FilterLookup = function(source, target)
{
if (IsNull(source) || IsNull(target)) { return; }
var name = IsNull(source.DataValue) ? '' : source.DataValue[0].name;
target.additionalparams = 'search=' + name;
}

• On the OnChange event of the Parent Account lookup mention the below code.

/* onChange() */
FilterLookup(crmForm.all.parentaccountid, crmForm.all.primarycontactid);

Note : Before you can see the code working, check the Parent Customer checkbox in the Contact Lookup View. Steps ->

• Settings > Customization > Customize Entites > Contact > Forms & Views > Contacts Lookup View
• Click on Add Find Columns on the right
• Tick Parent Customer
• Click OK and Publish

After performing the above mentioned, I select "A Bike Store" as the Parent Account and click on the Primary Contact Lookup.

The Contact lookup opens(as shown in the figure below) and you can see "A Bike Store" in the search box & CRM is only returned those Contact records whose Parent Customer is "A Bike Store."

Microsoft Dynamics CRM “V.Next” [5]

The investments for the next release of Microsoft Dynamics CRM fall into three broad categories:

Deliver a new level of user productivity and collaboration capabilities

Continued enrichment of the core CRM capabilities

Provide a best-of-breed business solution platform

Development and testing is in progress for Microsoft Dynamics CRM “V.Next” which encompasses several milestone builds before various external feedback and testing programs are initiated with customers and partners in the lead-up to general release. There is an exhaustive list of investments in Microsoft Dynamics CRM “V.Next” which ranges from small “tweaks” and enhancements to broad new feature areas. The following sections provide a summary of some of the investments across the three categories.

“V.Next” to deliver a new level of user productivity and collaboration capabilities

Customers, partners and the analyst community continue to agree that the primary reason why a CRM solution may fail is simply that the users within an organization don’t use the software! A key product strategy for Microsoft Dynamics CRM “V.Next” is to continue to provide a CRM solution that users want to work with, is as familiar as their regular desktop software such as Microsoft Office and allows them to more effectively manage their day-to-day commitments and customer interactions regardless of their role. Building on the success of Dynamics CRM 4.0, Microsoft is committed to further investing in a rich and satisfying user experience leveraging both Microsoft Office and Windows.

Continue to improve the end-user experience: focus on providing further flexibility for a user to set up their role-based view of the system quickly. With each new release of Dynamics CRM Microsoft has reshaped how CRM functionality can be delivered through Microsoft Office Outlook to drive a more natural user experience. Microsoft Dynamics CRM “V.Next” will further enhance the user experience and information view of CRM data within Microsoft Office Outlook to ensure simplicity and ease of use.

Increase accessibility through the Microsoft Office “ribbon” interface: provide a user experience that is consistent with established Microsoft Office designs such as the ribbon interface. This style of interface is designed to increase efficiency and make it easier for users to find features to get their work done. 

https://mbs.microsoft.com/partnersource/marketing/statementofdirection/MD_CRM_SOD.htm

How to Configure Microsoft Dynamics CRM 4.0 E-mail Router (On-Premise) with Microsoft Exchange Server 2010

Update Rollup 8 for Microsoft Dynamics CRM E-mail Router (On-Premise) includes support for Microsoft Exchange Server 2010. In continuation to the blog titled “Configure Microsoft Dynamics CRM Online E-mail Router with Exchange Online”, this one explains the detailed steps required to setup Microsoft Dynamics CRM 4.0 E-mail Router (On-Premise) with Microsoft Dynamics CRM 4.0 On-Premise users and queues having mailboxes in Microsoft Exchange Server 2010.
Microsoft Exchange Server 2010 replaces the WebDAV functionality with Exchange Web Services (EWS). Microsoft Dynamics CRM 4.0 E-mail Router (On-Premise) with Update Rollup 8 has been enhanced to integrate EWS support and hence function with Microsoft Exchange Server 2010. The E-mail Router maintains compatibility with Exchange 2003 (only WebDAV) and Exchange 2007 (both WebDAV and EWS).
Prerequisites

• Microsoft Dynamics CRM 4.0 On-Premise installation.
• Microsoft Exchange Server 2010.
• Microsoft Dynamics CRM 4.0 E-mail Router (On-Premise) with Update Rollup 8 or higher.

Configuration Steps
Microsoft Exchange Server 2010
Granting Exchange Impersonation permissions.
Microsoft Exchange Server 2010 makes do with the permissions model used in Microsoft Exchange Server 2007 and adopts the new Role Based Access Control (RBAC) allowing users to define extremely broad or extremely precise permissions models based on the roles of administrators and users. New commands are available to allow User/Mailbox Impersonation with varying scopes. Exchange Impersonation permission is required for a given Exchange 2010 account if it needs to cater to multiple Exchange 2010 accounts. The profile created with a user account having Exchange Impersonation permission can access the mailboxes of the users who are in the scope of this Exchange Impersonation permission.
In the Microsoft Exchange Server 2010 system, launch Exchange Management Shell from Start-> All Programs-> Microsoft Exchange Server 2010 -> Exchange Management Shell. The shell will connect to the Microsoft Exchange Server 2010 and display the prompt.
[PS] C:\Windows\System32>.

Example: impersonation scenarios
1. A single user is configured to connect to mailboxes of all other CRM users and queues that have their mailboxes on Microsoft Exchange Server 2010. This configuration hence makes do with the need to create profile for each CRM user and queue individually.
To achieve this you need to run the following command in Exchange Management Shell–
New-ManagementRoleAssignment   –Name: "ImpersonationName”
-User: "RouterAdministrator@YourOrganization.com"   –Role:"ApplicationImpersonation”
In the above command, the Name parameter specifies a name for the new management role assignment. User is the username of the user who is given Exchange Impersonation permission and therefore can now access Exchange 2010 mailboxes of all other users in the Exchange organization.
[Details on New-ManagementRoleAssignment can be found here]
2. A single user is configured to connect to mailboxes of select set of CRM users and queues that have their mailboxes on Microsoft Exchange Server 2010. This configuration is preferable as the impersonation rights are given selectively on the desired mailboxes only.
To enable this scenario, you need to define the set of users as a Management Scope in Microsoft Exchange Server 2010. To do so, run the following command in Exchange Management Shell–
New-ManagementScope   –Name: "ManagementScopeName" 
–RecipientRestrictionFilter { Name  -eq  ‘ crmuser1 ’ }
In the above command, The Name parameter specifies the name of the management scope. The RecipientRestrictionFilter parameter specifies the filter to apply to recipient objects.
[Details on New-ManagementScope can be found here]
The new Management Scope created can now be used in the Role Assignment command to restrict the scope of Exchange Impersonation.
New-ManagementRoleAssignment   –Name: "ImpersonationName”
-User: "RouterAdministrator@YourOrganization.com"   –Role:"ApplicationImpersonation”
-CustomRecipientWriteScope: ”ManagementScopeName”
Removing Exchange Impersonation permission.
Exchange Impersonation permission can be removed using the
Remove-ManagemntRoleAssignment command.
[Details on Remove-ManagemntRoleAssignment can be found here]
Microsoft Dynamics CRM
Configure users and queues to use Microsoft Dynamics CRM E-mail Router.
Users and Queues in CRM can be configured to use the E-mail Router for processing the incoming Exchange and outgoing CRM e-mails. To utilize this functionality, Users and Queues must have a valid email address and select E-mail Router as the incoming and outgoing E-mail access types. This can be setup by an administrator or users having relevant permissions.
CRM Users
1. Navigate to Settings->Administration->Users and configure the user record as displayed.

1. Individual users can select which e-mails from the specified Exchange On-Premise mailbox to Track in CRM. This can be selected from the Tools->Options-> E-mail tab.

CRM Queues

1. Navigate to Settings->Business Management->Queues and configure the Queue as displayed.
   

1. In line with Users, Queue form also provides the flexibility to choose the desired category of e-mails which need to be promoted to Microsoft CRM.
   

Microsoft Dynamics CRM 4.0 E-mail Router (On-Premise)
After the Router has been installed, launch the E-mail Router Configuration Manager from Start-> All Programs-> Microsoft Dynamics CRM E-mail Router. There are three main tabs in the Configuration Manager as shown below.

Configuration Profiles. To configure the E-mail Router, you first create one or more incoming and one or more outgoing configuration profiles. These configuration profiles contain information about the e-mail server and authentication methods that the E-mail Router will use to connect to the e-mail server and transfer e-mail messages to and from the Microsoft Dynamics CRM organization. You create configuration profiles on the Configuration Profiles tab in the E-mail Router Configuration Manager.
Deployments. After you create the configuration profiles that you want, you must define at least one deployment. The information that you enter into the Deployment area will be used by the E-mail Router to connect to your Microsoft Dynamics CRM deployment.
Users, Queues and Forward Mailboxes. After you have the configuration profiles and deployment established, then you manage the users, queues, and forward mailboxes that will be used by the E-mail Router to route Microsoft Dynamics CRM e-mail messages. You manage these items on the Users, Queues, and Forward Mailboxes tab in the E-mail Router Configuration Manager.
Creating Exchange Server 2010 incoming profile.

1. In the E-mail Router Configuration Manager tool, click the Configuration Profiles tab, and then click New.
2. Type a profile name. For example, type Exchange 2010 Incoming Email.
3. Choose Incoming in the Direction list.
4. Choose Exchange Web Services as the Protocol.
5. Choose Exchange 2010 as the E-mail Server Type.
6. The only Authentication Type allowed is “Windows Authentication”.
7. Type the name of the Microsoft Exchange Server 2010 web services URL.

Default Location
https://<Exchange-2010-Server-Name>/EWS/Exchange.asmx

8. Select how the e-mail Router will gain access to the Microsoft Exchange Server 2010 in the Access Credentials list.

• If you select Local System Account for the Profile, the Router will use the credentials specified in the Microsoft CRM Email Router service running in the host machine. The credentials provided should be the username of user in your Microsoft Dynamics CRM organization who has the System Administrator role. This user must have Exchange Impersonation permission on the mailboxes that this Incoming Profile will serve including self. This type of profile is typically used for polling large number of mailboxes using the credentials of a user with Administrative privileges and Exchange Impersonation permissions.
• If you select User Specified for the Profile, the Router will use the user name and password provided in Microsoft Dynamics CRM for users who are configured to use this Incoming Profile.
• If you select Other Specified for the Profile, the Router will use the user name and password provided in the open textboxes as shown below. User name has to be provided in the form DomainName\UserName. The specified user must have Exchange Impersonation permission on all the mailboxes that this Incoming Profile will serve (Exchange Impersonation Permissions on self is not required).

Note: The above steps can also be used to create an incoming profile for a CRM user having Microsoft Exchange Server 2007 mailbox by choosing Exchange 2007 as the Email Server Type in step 5.
Creating Exchange Server 2010 outgoing profile.
Microsoft Dynamics CRM 4.0 Email Router (On-Premise) with Update Rollup 8 supports SMTP as the default and only protocol for outgoing e-mail messages as in the case of previous versions.

1. In the E-mail Router Configuration Manager tool, click the Configuration Profiles tab and then click New.
2. Type a profile name. For example, type Exchange 2010 Outgoing Email.
3. Choose Outgoing in the Direction list.
4. The only Protocol allowed is SMTP.
5. Verify that SMTP is selected as the E-mail Server Type.
6. Choose the Authentication Type as appropriate.

1. Type only the name of the Microsoft Exchange Server 2010 system in the Location field.
2. Check SSL box if the Microsoft Exchange Server 2010 uses SSL for SMTP.
3. Select and provide the appropriate Access Credentials with Exchange Impersonation permission as required. [See section on Granting Exchange Impersonation permission for details]

Configure the Microsoft Dynamics CRM On-Premise deployment.
After you have created the outgoing and incoming e-mail profiles, click the Deployments tab in the E-mail Router Configuration Manager tool.

1. Click New to create a new deployment. The default Deployment option will be set to My Company.
2. In the Microsoft Dynamics CRM Server open text box it will default to http://discovery/<OrganizationName>. Replace discovery with the name of the Microsoft Dynamics CRM On-Premise Server and <OrganizationName> with your Microsoft Dynamics CRM Organization Unique Name.
   Note: The Organization Unique Name is case-sensitive.
3. Verify that Microsoft Dynamics CRM secure URL Port contains valid value if the CRM server is SSL enabled.

1. Select how the e-mail Router will gain access to the Microsoft Exchange Server 2010 in the Access Credentials list.

• If you select Local System Account, the Router will use the credentials specified in the Microsoft CRM Email Router service running in the host machine.
• If you select Other Specified, the Router will use the user name and password provided in the open textboxes as shown below. User name has to be provided in the form DomainName\UserName.

    5. In the Incoming configuration profile, select the incoming profile you created.

1. In the Outgoing configuration profile, select the outgoing profile you created.
   Note: Setting the Incoming and Outgoing configuration profiles on the Deployment will make these the default profiles for the users that are set to use the E-mail Router for incoming and outgoing e-mail. You can change it for each user in the Users, Queues and Forward Mailboxes tab.
2. Click OK to finish creating the deployment.

Forward Mailbox
Forward Mailbox is one of the options available for processing the incoming e-mails in Microsoft CRM. This option is helpful in scaling the system where all the Forward Mailbox users and queues have all their e-mails forwarded to the Forward Mailbox using Exchange forwarding rules. Emails for multiple users and queues are present in this single E-mail box as an attachment and hence Router can promote them to Microsoft Dynamics CRM using the single polling location. Users and Queues can have this options set for incoming e-mails processing as follows.

• Users: Settings->Administration->Users
• Queues: Settings->Business Management-> Queues

Set up the Forward Mailbox.

1. Open the Microsoft Dynamics CRM E-mail Router Configuration tool.
2. Click the Users, Queues and Forward Mailboxes tab.
3. In the Select a CRM Deployment to view users and mailboxes list, select the Microsoft Dynamics CRM deployment you created.

1. Click Load Data. This will display the Microsoft Dynamics CRM users who are configured to use the Email Router for processing their e-mails.
   Note: If you receive an error displaying the users, verify the correct organization name is listed in the Select a CRM Deployment to view users and mailboxes list. Also, verify the organization name is entered with the correct case. The organization name is case-sensitive.
   Note: If no users are listed after you click Load Data, or if you are missing users, check the user’s settings by following the steps in the section titled “Configure users and queues to use Microsoft Dynamics CRM E-mail Router.”
2. Click the Forward Mailboxes tab, and then click the New.
3. Type a name for the forward mailbox profile. For example type ForwardMailbox in the Name open text box.
4. Type the e-mail address for the forward mailbox in the E-mail Address open text box.
5. Click OK. 

Deploy Exchange rules manually through Microsoft Exchange Server 2010.
In order to use the forward mailbox feature Microsoft Exchange Server 2010 users need to manually create rules on their own mailboxes from OWA or using Outlook client. This can be done by using the Rule Deployment Wizard for Microsoft Exchange Server 2007 and earlier systems. In Microsoft Exchange Server 2010 they will need to manually setup a rule with the following logic:

Forward All e-mails as An Attachment to <a mailbox you defined in your system>
This rule will forward all incoming e-mail to the Microsoft Dynamics CRM forwarding mailbox. After the rules have been deployed, any e-mail that is received in a user’s mailbox will be forwarded as an attachment to the forwarding mailbox. The Microsoft Dynamics CRM E-mail Router Service monitors the forward mailbox. The service will route Microsoft Dynamics CRM e-mail to Microsoft Dynamics CRM as an e-mail activity. If the e-mail is not related to Microsoft Dynamics CRM, the service will delete the e-mail message from the forwarding mailbox.
Test and publish the new incoming /outgoing profiles and deployment.
The final step is to publish new incoming profiles, the deployment and forward mailbox settings. Before publishing, connectivity to all mailboxes using the specified profiles must be tested. To do this, complete the following steps:

1. Click the Users, Queues and Forward Mailboxes tab within the E-mail Router Configuration Manager tool.
2. In the Select a CRM Deployment to view users and mailboxes list, select the Microsoft Dynamics CRM deployment you created.
3. Click Load Data. This will display the Microsoft Dynamics CRM users configured to use the e-mail Router.

Note: If you receive an error loading the data, verify the correct organization unique name is listed in the Select a CRM Deployment to view users and mailboxes list. Also, verify the organization unique name is entered with the correct case. The organization unique name is case sensitive. If no users are listed after you click Load Data, or if you are missing users, check the user’s settings. Also Forward Mailbox users and queues do not have the option of assigning the incoming profiles because the forward mailbox is directly used for the incoming E-mail processing.

1. If you want to change the Incoming or Outgoing configuration profiles for certain users, double click the user and change the selection for the Incoming Configuration Profile or Outgoing Configuration Profile and click OK.
2. Click Test Access. Tests will be performed on all users for both profiles. A successful test will display a green succeeded message that resembles the following:
   
3. To publish the deployment, click Publish. A successful publish will display the following message: 

On publishing the Router will start catering the Microsoft CRM Users and Queues having the Microsoft Exchange Server 2010 mailboxes.
Cheers,


 [http://blogs.msdn.com/crm/archive/2009/12/21/how-to-configure-microsoft-dynamics-crm-4-0-e-mail-router-on-premise-with-microsoft-exchange-server-2010.aspx]

Change Dynamics CRM 4.0 Logo

I've been asked to change a certain organization logo, and I've googled it and found the same result:

although this is still not a supported customization, it's still doable. referencing from Cesar de la Torre blog, here are the ways to do it.

1. change the image file at [C:\Program Files\Microsoft CRM Server\CRMWeb\_imgs\masthead.jpg] and you are done.
or
2. modify the css definition [TD.ms-crm-MastHead-Logo] at [C:\Program Files\Microsoft CRM Server\CRMWeb\_common\styles\global-dynamic-styles.css.aspx] file.

be sure to backup those settings when you are upgrading to new versoin of CRM or applying a patch, since the update might then overwrite your files and lost your logo custimization.
 --------------------------- this is the end for the post I found,

but the above solution actually changes the logo for all organizations, to change it for certain organization you can navigate to [C:\Program Files\Microsoft CRM Server\CRMWeb\_common\styles\global-dynamic-styles.css.aspx] file and start editing the class TD.ms-crm-MastHead-Logo to include the organization check:

<% if (Request.Url.ToString().ToLower().Contains("<your custom organization name>")) { %>
background-position: top right;
background-image: url(/_imgs/<your custom logo>.jpg);
<% } else { %>
background-position: top left;
background-image: url(/_imgs/masthead.jpg);
<% } %>

and you can do the same for the CSS class for the rest of the colors and backgrounds.

Many to Many Relationship IFrame

you can display the N-N Relationship view or any other view in CRM entity in IFrame like this:

to do this, I am creating two test entities new_testentity1 and new_testentity2 and many to many relationship between the two entities, and IFrame in new_testentity1  named IFRAME_TestEntity2
and form onload script:

function OnCrmPageLoad() {
            /* Create a N2NViewer and give it the IFRAME (container) id */
            var n2nViewer = new N2NViewer('IFRAME_TestEntity2');
            /* Set the role order - use iedevtoolber for exact parameters */
            n2nViewer.RoleOrder = 1;
            /* assing the relationship name (without the "area" word) */
            n2nViewer.TabsetId = "new_new_testentity1_new_testentity2";
            /* Do the trick... */
            n2nViewer.Load();
        }

        function N2NViewer(iframeId) {
            if (!document.all[iframeId]) {
                alert(iframeId + " is missing!");
                return;
            }

            var viewer = this;
            var _locAssocObj = null;

            viewer.IFRAME = document.all[iframeId];
            viewer.RoleOrder;
            viewer.TabsetId;

            viewer.Load = function() {
                /* Construct a valid N2N IFRAME url */
                viewer.IFRAME.src = "areas.aspx?oId=" + crmForm.ObjectId + "&oType=" + crmForm.ObjectTypeCode + "&security=" + crmFormSubmit.crmFormSubmitSecurity.value + "&roleOrd=" + viewer.RoleOrder + "&tabSet=area" + viewer.TabsetId;
                viewer.IFRAME.onreadystatechange = viewer.StateChanged;
            }

            viewer.StateChanged = function() {
                if (viewer.IFRAME.readyState != 'complete') {
                    return;
                }

                var iframeDoc = viewer.IFRAME.contentWindow.document;

                /* Reomve scrolling space */
                iframeDoc.body.scroll = "no";
                /* Remove crmGrid Default padding */
                iframeDoc.body.childNodes[0].rows[0].cells[0].style.padding = 0;

                /* Save MS locAssocObj */
                _locAssocObj = locAssocObj;
                /* Override MS locAssocObj */
                locAssocObj = viewer.locAssocObj;
            }

            viewer.locAssocObj = function(iType, sSubType, sAssociationName, iRoleOrdinal) {
                /* Open the Dialog */
                _locAssocObj(iType, sSubType, sAssociationName, iRoleOrdinal);
                /* Refresh only if our iframe contains the correnct tabset name */
                if (sAssociationName == viewer.TabsetId) {
                    viewer.IFRAME.contentWindow.document.all.crmGrid.Refresh();
                }
            }
        }

        //Entry Point
        OnCrmPageLoad();