«Connector for Microsoft Dynamics® Installation Guide June 2014 Find updates to this documentation at the following location: ...»
4. Enter the URL for the Microsoft Dynamics CRM Discovery Service.
5. Enter the domain, user name, and password for the CRM Deployment Administrator account or the Administrator account for Microsoft Dynamics CRM online. For more information about this account, see CRM Deployment Administrator account.
6. Click Get Organizations.
CONNECTOR FOR MICROSOFT DYNAMICS® INSTALLATION GUIDE
7. Select the organization to configure. The Microsoft Dynamics CRM Configuration utility must be run for each organization to integrate.
8. Click Next.
9. Select the Microsoft Dynamics CRM entities to configure for integration. The preselected entities are those that are required for the standard out-of-the-box integration to run. If you have custom Microsoft Dynamics CRM entities to configure for integration, they are included in the entity list that is displayed. To view the available entities, click the plus sign (+) next to the organization name.
Select the check box next to each entity to configure. To add more entities later, run the utility again.
10. If this is not the first time that you are running the adapter configuration, and if you are adding a new entity or are making other changes to the adapter configuration, select the Skip complete configuration and only generate entity configurations check box.
11. Click Next.
12. When the Configuration status for organization page is displayed, click Configure. If a message is displayed that indicates that existing customizations will be overwritten, click OK to continue.
13. When the “Finished updating organization” message is displayed, click Finish to exit the utility.
Note: After configuration is completed, customizations are published for Microsoft Dynamics CRM.
If you created customizations using the Microsoft Dynamics CRM Configuration utility, those customizations might be published after configuration is completed.
Tips for configuring Microsoft Dynamics CRM You can run the Microsoft Dynamics CRM Configuration utility at any time to configure new organizations in Microsoft Dynamics CRM. To open the Configuration utility, open Connector for Microsoft Dynamics, and then click Adapter Settings. In the Adapter Settings window, select the version of Microsoft Dynamics CRM that you are integrating with, and then click Configure Microsoft Dynamics CRM.
If you run the Configuration utility after you have registered the Microsoft Dynamics CRM adapter, some fields in the Configuration utility might already contain values. These values are based on the information that you provided when you configured the Microsoft Dynamics CRM adapter.
If you have a distributed Microsoft Dynamics CRM on-premise deployment, you must restart IIS on all Microsoft Dynamics CRM servers, including application and SDK servers, after completing the utility.
If you delete an object provider file for a static customizable Microsoft Dynamics CRM entity from the company folder in the ObjectConfig folder, running the Microsoft Dynamics CRM Configuration utility again will not re-create the object provider correctly. This will cause the Microsoft Dynamics CRM Adapter to fail to load.
A copy of each static Microsoft Dynamics CRM object provider file is copied to the ObjectProvider folder. You will need to copy the object provider file for the affected entity from the ObjectConfig folder back into the company folder.
Static customizable Microsoft Dynamics CRM entities are: AccountObjectProvider, ContactObjectProvider, ErpSystemUserObjectProvider, InvoiceObjectProvider, OrderObjectProvider, and ProductObjectProvider.
Microsoft Dynamics CRM 4.0 might cache information that causes the Test Settings option to return incorrect results.
If you click Test Settings before the CRM Integration User has been added to the PrivUserGroup for the Microsoft Dynamics CRM 4.0 organization that you want to integrate on the domain that the Microsoft Dynamics CRM server is joined to, the Test Settings operation will fail until the client is closed and re-opened.
CONNECTOR FOR MICROSOFT DYNAMICS® INSTALLATION GUIDEIf the user running the Configuration utility is not a domain administrator for the domain that the CRM Integration User and Microsoft Dynamics CRM server are members of, a warning will be displayed. Until this CRM Integration user is added to the PrivUserGroup, the Test Settings operation will always fail and the integration will not work. Adding the CRM Integration user to the PrivUserGroup may be completed by a domain administrator prior to running the Configuration utility or after it has been run. If you add the CRM Integration user to the PrivUserGroup after you run the utility, you must close and restart the client before the Test Settings operation will return valid results.
This issue occurs because Microsoft Dynamics CRM uses the WindowsPrincipal.IsInRole method to check if the user attempting to access Microsoft Dynamics CRM is in the PrivUserGroup in the current Domain. The WindowsPrincipal.IsInRole method caches the last result for a given user until the user and caller both log off and log back on to the domain. For more information, see “WindowsPrincipal.IsInRole Method (String)” on MSDN (http://msdn.microsoft.com/enus/library/fs485fwh.aspx).
If you are integrating with Microsoft Dynamics CRM 4.0, you must set up duplicate detection for the address entity in Microsoft Dynamics CRM 4.0. For more information, see Set up duplicate detection.
Note: Duplicate detection for addresses in Microsoft Dynamics CRM 2011 is actually enabled during installation.
If you select to install the customization provided with the Microsoft Dynamics CRM adapter, you will overwrite any existing form customizations which have been created for account, contact, product and any of the other Microsoft Dynamics CRM 4.0 entities which are updated to enable the integration.
For new installations with no existing customizations, this should not be an issue and the option to import the customization should be selected.
For existing Microsoft Dynamics CRM 4.0 installations where customizations have been applied, registration for Connector for Microsoft Dynamics can continue without importing the Microsoft Dynamics CRM customizations. However, the existing customizations and required new customizations will need to be merged before they are imported into Microsoft Dynamics CRM. This merge process can be accomplished by using the tool and related readme which are available from the download site for Connector for Microsoft Dynamics.
When the merge process is complete, you must import customizations. Data cannot be successfully integrated until these customizations are integrated into Microsoft Dynamics CRM 4.0. In Microsoft Dynamics CRM 4.0, click Settings, click Customizations, and then select Import Customizations.
Note: If you are using the Microsoft Dynamics CRM 2011 adapter, these customizations are automatically installed during configuration and merged with your existing customizations in Microsoft Dynamics CRM 2011. No further action is necessary.
Changes made by the Microsoft Dynamics CRM Configuration utility If you run the Microsoft Dynamics CRM Configuration utility, the following changes are made to each Microsoft Dynamics CRM organization that you selected for configuration.
Note: Before the Microsoft Dynamics CRM adapter Configuration utility makes any changes to Microsoft Dynamics CRM, it saves your existing customizations to C:\ProgramData\Microsoft Dynamics\Connector for Microsoft Dynamics. You can remove these customizations and revert to your previous customizations if you uninstall the product. If you remove the customizations, any of the custom entities that contain data will not be removed.
A Submit Order button is added to the Order form. This button appears only for users who are in roles that have the ISVExtenstions privilege enabled for the organization.
All prices and price lists are set to read-only.
CONNECTOR FOR MICROSOFT DYNAMICS® INSTALLATION GUIDE All entities in the Product Catalog are set to read-only.
All unit groups and units are set to read-only.
Any existing products, discount types, price levels in the Product Catalog are deactivated and renamed.
The invoice functionality is limited to read-only within Microsoft Dynamics CRM.
The default decimal precision is set to four decimal places.
Note: You can change this setting if you want your Microsoft Dynamics CRM pricing decimal precision to be less than four. The Microsoft Dynamics CRM pricing decimal precision should match your Microsoft Dynamics ERP currency decimal precision to prevent rounding issues. Microsoft Dynamics ERP currency decimal precision can be set up to five while Microsoft Dynamics CRM can be set up to four.
Integration key attributes are added to the entities selected on the Select the entities to
configure for integration window. The following entities are pre-selected by default:
Account o Contact o Invoice o Order o Product o ERP system user o Note: Certain system entities are not available for customization and will not have an Integration Key attribute added to them. For these entities, the name attribute is mapped internally to the Integration Key attribute from the ERP source system.
The following custom entities are added:
ERP System User – For tracking salespersons in the ERP system o *Account* – For tracking accounts that have been integrated and then deleted from Microsoft o Dynamics CRM *Contact* – For tracking contacts that have been integrated and then deleted from Microsoft o Dynamics CRM The isSOPIntegrated attribute is set to true for each organization to be integrated.
A Ready for Integration check box is added to the Administration tab on the Account form.
An Integration Key attribute is added to the Administration tab on the Account form.
A Submit button is added to the Account form.
A Ready for Integration check box is added to the Administration tab on the Contact form.
A read-only Integration Key field is added to the Administration tab on the Contact form.
A Submit button is added to the Contact form.
A control is added to the User form that allows users to map an integrated ERP system user to an existing Microsoft Dynamics CRM user.
CONNECTOR FOR MICROSOFT DYNAMICS® INSTALLATION GUIDE An Order entity is validated to ensure that a customer is ready for integration or that the customer is able to be integrated, if it is not already integrated when the order is submitted.
A plug-in is registered in Microsoft Dynamics CRM.
The Microsoft Dynamics Integration security role is created.
The following privileges are removed from all security roles that they are associated with:
AppendInvoice o AssignInvoice o CreateInvoice o CreateProduct o DeleteInvoice o DeleteProduct o OverridePriceEngineInvoice o ShareInvoice o WriteInvoice o WriteProduct o When using a Microsoft Dynamics CRM online deployment, the user specified as the CRM Integration account will be set to have an access mode of Non-interactive and will be flagged as an integration user.
A Bulk Submit Accounts on-demand workflow is added, which allows you to select multiple accounts, and then submit them to the ERP system.
A Bulk Submit Contracts on-demand workflow is added, which allows you to select multiple contracts, and then submit them to the ERP system.
If a primary contact has been associated with an account in Microsoft Dynamics CRM, and that contact has not been submitted to the ERP system, a message is displayed when you submit the account that indicates that the primary contact must be submitted before the account. If a nonsubmitted contact is added as the primary contact of a submitted account in Microsoft Dynamics CRM, the account cannot be updated in the ERP system by Connector, and the update will fail.
If a parent account has been associated with a contact, and the parent account has not been submitted to the ERP, a message is displayed when you submit the contact that indicates that the parent account must be submitted before the contact. If a nonsubmitted account is added as the parent account to a submitted contact in Microsoft Dynamics CRM, the account record cannot be updated in the ERP system by Connector, and the update will fail.
CONNECTOR FOR MICROSOFT DYNAMICS® INSTALLATION GUIDESet up duplicate detection Note: If you do not have existing installations of both Microsoft Dynamics CRM and a Microsoft Dynamics ERP system, then you may skip this procedure.
When you integrate data between existing installations of Microsoft Dynamics CRM and a Microsoft Dynamics ERP system, you might have duplicate records between the two applications. For example, if you have entered Bob Kelly as a contact in Microsoft Dynamics CRM and also as a customer in the Microsoft Dynamics ERP database, then you have duplicate records.
Microsoft Dynamics CRM allows users to enter duplicate records, with duplicate keys, for Microsoft Dynamics CRM accounts and contacts. This can cause problems when the integration service tries to integrate the records.
If duplicated records are not identified before you integrate Microsoft Dynamics CRM contacts or accounts with your Microsoft Dynamics ERP customers, you will end with four records for the same person between the two applications.
When you use duplicate detection rules, and a duplicate record is identified during an integration, the Microsoft Dynamics CRM adapter updates the entity in Microsoft Dynamics CRM instead of creating multiple entities. The record in the ERP database is not affected.
To prevent duplicate record records from entering the system during initial data synchronization, use one of the following options.
Set up duplicate detection rules in Microsoft Dynamics CRM In Microsoft Dynamics CRM, set up or modify duplicate detection rules for the entities to integrate.