Open topic with navigation

You are here: Chapter 13: FootPrints CRM Bridge > MS CRM Integration > Configuration of Contact Issue History in Microsoft CRM

Configuration of Contact Issue History in Microsoft CRM

FootPrints can easily be integrated with Microsoft CRM, a web-based sales force automation solution. From within MS CRM, sales representatives can see active support issues for individual customers within their contacts list.  For more information on MS CRM, visit the Microsoft Dynamics CRM TestDrive Demo site.

Configuring FootPrints Integration with MS CRM

For FootPrints Integration with MS CRM, two files are delivered to the MS CRM administrator.  These are:

A version of each of these files already exists within the MS CRM installation.  The steps for configuring MS CRM 1.2 and MS CRM 3.0 (and higher) are different.  Both procedures are described below.

MS CRM 1.2

Step 1

The MS CRM administrator must rename the current web.config file, located in \inetpub\wwwroot\, to something like web.config.old and copy or move the new web.config file to \inetpub\wwwroot\.

Step 2

The MS CRM administrator must:

  1. Rename the isv.config file, located in \inetpub\wwwroot\_Resources\, to something like isv.config.old and copy or move the new isv.config file to \inetpub\wwwroot\_Resources\.
  2. Open the new isv.config file with an editor such as Notepad.
  3. Find the line:

Url="http://footprints.servername.com/MRcgi/MRentrancePage.pl" Id="navItem"/>

and change footprints.servername.com to the server on which FootPrints is installed.

  1. Save and close the file.

FootPrints Integration with MS CRM 1.2 is now complete.  You can begin to view FootPrints Issues from within MS CRM.

MS CRM 3.0 and Higher

Step 1

The files that the administrator must change are located under the web site's home directory. For example, this might be C:\Program Files\Microsoft CRM\CRMWeb for the web.config file and C:\Program Files\Microsoft CRM\CRMWeb\_Resources for the isv.config.xml file.

Step 2

The MS CRM administrator must:

  1. Rename the isv.config.xml file, located in C:\Program Files\Microsoft CRM\CRMWeb\_Resources, to something like isv.config.old and copy or move the new isv.config.xml file to \inetpub\wwwroot\_Resources\.
  2. Open the new isv.config.xml file with an editor such as Notepad.
  3. Find the line:

<Entity name="contact" />

and change it to the following:

Entity name="contact">

<NavBar>

<NavBarItem Icon="/_imgs/ico_16_112.gif" Title="FootPrints Cases" Url="http://footprints.servername.com/MRcgi/MRentrancePage.pl" Id="navItem" /> </NavBar> </Entity>

where footprints.servername.com is the server on which FootPrints is installed.

  1. Save and close the file.
  2. Open the new web.config file, located in \inetpub\wwwroot\, with an editor such as Notepad.
  3. Find the line:

<add key="ISVIntegration" value="None"/>

and change it to:

<add key="ISVIntegration" value="Web"/>

  1. Save and close the web.config file.

FootPrints Integration with MS CRM 3.0 and higher is now complete.  You can begin to view FootPrints Issues from within MS CRM.

 

©Copyright 1999, 2009 BMC Software, Inc. © Copyright 1996 - 2017 BladeLogic, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. FootPrints is the exclusive property of BladeLogic, Inc. and is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.BladeLogic, Inc. and BMC Software, Inc. Confidential. Click here for the installation guide which includes the provisions described in the BMC License Agreement and Order related to third party products or technologies included in the BMC Product.