November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
This document describes the necessary steps to install the EPiServer 7 Connect for CRM and EPiServer 7 Connect for CRM Templates using the EPiServer Deployment Center.
Check the system requirements for EPiServer 7 Connect for CRM before you start the installation, to ensure that the system requirements are met for the target environment.
The following installation packages are available for EPiServer Connect for CRM module:
This package is the actual module Connect for CRM. It contains implementation of loading and saving data in CRM system, storing and synchronizing user profile information on web site and in CRM application and virtual role provider based on CRM entity properties.
This package contains shared block, business logic and presentation components that allow managing registration and profile editing for site users. The package includes source code and should be installed on top of Connect for CRM.
Consider following after-installation steps.
In order to complete Connect for CRM configuration, please refer to the tech note Configuring EPiServer 7 Connect for CRM. For example, you may need to setup user profile properties that should be connected to contact data in CRM system.
You can customize which fields should be displayed on entity form in CRM system, so you can add custom fields that were created during customization installation to the contact forms. Login to Microsoft Dynamics CRM, go to Settings, navigate to Customizations and click Customize the System (Customize Entities in MS Dynamics CRM 4.0). Select Contact entity and edit required Forms. Add fields that should be displayed on form: User name, Low, Medium and High.
Publish your customizations.
Login to SalesForce CRM, go to Setup and navigate to App Setup / Customize / Contacts / Page Layouts section. Edit page layout where custom fields need to be displayed. You can create new section and add custom fields that were created during the customization package installation: User name, Low, Medium and High.
Please refer to Using EPiServer 7 Connect for CRM Templates article.
By default customizations and plug-in are installed when you run Connect for CRM installation using Deployment Center and corresponding options are selected in installation wizard. Refer this section if you need to manage customizations and plug-in manually.
Customizations and plug-in are deployed during Connect for CRM installation if Install customizations and synchronization plug-in for Microsoft Dynamics CRM option is selected.
You can install it manually by running PowerShell script Install MS CRM Customizations.ps1. The script is located in Connect for CRM installation folder, usually the path is C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\Install\Modules\ConnectForCRM\Install MS CRM Customizations.ps1. Please look at file content for more information about required script parameters, like CRM web service URLs, user credentials and so on. For example:
Powershell "& '.\Install MS CRM Customizations.ps1'" -crmServiceUrl "http://internal.example.com:5555/mscrmservices/2007/crmservice.asmx" -metadataServiceUrl "http://internal.example.com/mscrmservices/2007/metadataservice.asmx" -crmOrganizationName "Organization" -crmDomain "Example" -crmUserName "CrmUser" -crmPassword "CrmUserPassword" -synchronizationServiceUrl "http://example.com/modules/ConnectforCrm/SynchronizeService.svc" -synchronizationUserName "SiteServiceUser" -synchronizationPassword "SiteServiceUserPassword" -resourcesPath ".\bin" -solutionsDataFilePath ".\PluginSolutions.xml"
You may have to specify full path to Connect for CRM installation directory instead of relative path .\ when you run script from outside of that folder.
Consider adding .NET 4.0 to the list of supported runtimes if you face with assembly loading exception like "This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." In this case you need to create or edit PowerShell.exe.config file in directory where PowerShell.exe resides. Typical location is C:\Windows\System32\WindowsPowerShell\v1.0\. You need edit or create configuration file in folders of 32 and 64 bit versions of PowerShell if you use both of them. Make sure that .NET 4.0 is in the list of supported runtimes:
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319"/>
<supportedRuntime version="v2.0.50727"/>
</startup>
</configuration>
You can use CRM Plugin Registration Tool to manage synchronization plug-in for Microsoft Dynamics CRM manually. This tool is also included in Microsoft Dynamics CRM 2011 SDK.
CRM entity metadata like information about available contact fields is cached on CMS side. Consider restarting your website after changing CRM data structures, for example after installing or uninstalling customizations.
Customizations installation is initiated during Connect for CRM installation if Install customizations for SalesForce CRM option is selected.
You can install customizations manually by running PowerShell script Install SalesForce Customizations.ps1. The script is located in Connect for CRM installation folder, usually the path is C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\Install\Modules\ConnectForCRM\ Install SalesForce Customizations.ps1. This script does not require any parameters.
Consider adding .NET 4.0 to the list of supported runtimes as it is described in previous topic if you face with assembly loading exception like "This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded."
CRM entity metadata like information about available contact fields is cached on CMS side. Consider restarting your website after changing CRM data structures, for example after installing or uninstalling customizations.
Last updated: November 11, 2013