Microsoft Dynamics CRM Connector for Microsoft Dynamics GP

Readme

November 2006


This document provides important, late-breaking information about this release of Microsoft Dynamics CRM Connector for Microsoft Dynamics GP that supplements the Microsoft Dynamics CRM Connector for Microsoft Dynamics GP Guide.

Contents

Contents of the Download and CDs

Microsoft CRM Connector for Microsoft Dynamics GP Documentation

Installation Prerequisites

Known Issues

Documentation Feedback

Contents of the Download and CDs

The following table lists the contents of the download files and CDs.

Name

Contains

Microsoft CRM Connector for Microsoft Dynamics GP

·         Release Notes

·         Microsoft CRM Connector for Microsoft Dynamics GP Guide

·         Microsoft CRM Connector for Microsoft Dynamics GP Setup

Microsoft CRM Connector for Microsoft Dynamics GP Documentation

To get started, read the Microsoft CRM Connector for Microsoft Dynamics GP Implementation Guide, which contains detailed instructions for installing the release of Microsoft CRM Connector for Microsoft Dynamics GP. This guide is written for the team of people responsible for implementing Microsoft CRM Connector for Microsoft Dynamics GP and provides information for a new installation or upgrade from version 1.2/1.8.  

To download the guide, click the following link:

http://go.microsoft.com/fwlink/?LinkID=63047&clcid=0x409

The Microsoft CRM Connector for Microsoft Dynamics GP Guide is divided into three parts:

Part 1: Overview and Installation

·        Chapter 1: Introduction.

·        Chapters 2 and 3: Overview and installation of Microsoft CRM Connector for Microsoft Dynamics GP. These chapters cover the supported server platform configurations and installation procedures.

Part 2: Integrating Entities

·        Chapters 4 through 6: These chapters are designed to help you understand how entity data transfers occur with customers, accounts, contacts, products, orders, invoices, and pricing.

Part 3: Customizing, Operating, and Troubleshooting

·        Chapter 7: Microsoft CRM Connector for Microsoft Dynamics GP tools. This chapter details how to use each tool that is included with Microsoft CRM Connector for Microsoft Dynamics GP.

·        Chapter 8: Customizing Integration. This chapter explains how to customize integration and provides examples.

·        Chapter 9: Operating and Maintaining. This chapter describes best practices on how to maintain your integration system.

·        Chapter 10: Troubleshooting. This chapter describes the issues that may occur when you install or use Microsoft CRM Connector for Microsoft Dynamics GP and the steps to take to resolve those issues.

Installation Prerequisites

·        Windows Server 2000 computers must have Systems Management Server (SMS) 2003 Service Pack 1 (SP1) Updated Advanced Client installed before installing the Microsoft CRM Integration Server component through the Microsoft CRM Connector for Microsoft Dynamics GP Setup. You can download Systems Management Server (SMS) 2003 Service Pack 1 (SP1) Updated Advanced Client at http://www.microsoft.com/downloads/details.aspx?FamilyID=4d0ab3df-c150-4cfe-bf33-40f4ca5278cb&DisplayLang=en.

·        Downlevel Client Support for Message Queuing must be installed and running on a Windows Server 2003 server computer that is running the Active Directory directory service and other servers (Microsoft CRM, Microsoft Great Plains, and Integration servers) that are running Windows Server 2000. This support can be installed from the Add or Remove Programs application in Control Panel. For instructions about how to install this component, see Message Queuing online Help. To open Message Queuing online Help on a computer that has Message Queuing installed, follow these steps:

1.      Click Start, click Run, type compmgmt.msc and then click OK. 

2.      In the Computer Management window, expand Services and Applications, and then right-click Message Queuing. 

3.      Click Help. 

·        Microsoft Internet Explorer 6 Service Pack 1 (SP1) must be installed.

·        Microsoft .NET Framework 1.1 SP1 must be installed.

·        See Chapter 3, “Installation Instructions,” in the Microsoft CRM Connector for Microsoft Dynamics GP Guide for additional installation prerequisites in addition to the Microsoft CRM updates listed in the following section.

Updates to Install

You must install the following updates.

Microsoft CRM Connector for Microsoft Dynamics GP Updates

Please visit the following Web site to get the latest updates and new information about this product.

http://www.microsoft.com/dynamics/crm/using/downloads/default.mspx

Microsoft CRM 3.0 Updates

Before you install Microsoft CRM Connector for Microsoft Dynamics GP, you must install, or have installed, the following Microsoft Dynamics CRM 3.0 updates. The following table lists the issue and provides a link to the update that resolves it.

Issue

Update

Error messages when you try to save or to close an appointment in Microsoft CRM 3.0: "An error has occurred" and "General failure in scheduling engine"

Microsoft Knowledge Base article 917010 available at http://support.microsoft.com/kb/917010/en-us

Error message in Microsoft Dynamics CRM 3.0: "SQL Server timeout expired"

Microsoft Knowledge Base article 913802 available at http://support.microsoft.com/kb/913802/en-us

Error message when you run a solution that sets the state of a request or of a response for an entity in Microsoft Dynamics CRM 3.0: "This method can only be called in the context of web service request"

Microsoft Knowledge Base article 924454 available at

 

http://support.microsoft.com/kb/924454/en-us

Data is lost when you accept the default system mappings between Microsoft Dynamics CRM and Microsoft Dynamics GP in the Microsoft Dynamics CRM Connector for Microsoft Dynamics GP

Microsoft Knowledge Base article 924581
available at http://support.microsoft.com/kb/924581/en-us

 eConnect Updates

It is recommended that you install the latest eConnect hot-fixes. You need to contact Microsoft CRM support for this purpose. If you are using Microsoft Dynamics GP 9.0, visit https://mbs.microsoft.com/partnersource/products/greatplains/downloads/releases/econnect9hotfixes.htm?printpage=false to obtain a list of eConnect 9.0 hot-fixes and instructions on how to obtain them.

If you are using Microsoft Business Solutions Great Plains 8.0, visit https://mbs.microsoft.com/partnersource/products/greatplains/downloads/releases/econnect8hotfixes.htm?printpage=false to obtain a list of eConnect 8.0 hot-fixes and instructions on how to obtain them.

After installing the eConnect updates some manual steps need to be performed. For details refer to Microsoft Knowledge Base article 926685 available at http://support.microsoft.com/kb/926685/en-us

 

Upgrade from the original Microsoft CRM Connector for GP release

If you are using the original release of the Microsoft CRM Connector for GP and want to upgrade to the re-release, use the steps detailed in Microsoft Knowledge Base article 926687 available at http://support.microsoft.com/kb/926687/en-us.

 

Known Issues

Issues, limitations, and unexpected behavior that have been discovered in Microsoft CRM Connector for Microsoft Dynamics GP are documented in “Chapter 10 Troubleshooting” and also in various other chapters in the “Known Issues” section of the Microsoft CRM Connector for Microsoft Dynamics GP Guide.

Issues resolved with this re-release

As a result of this re-release the following issues were resolved.

 

KB Article

Short Description

No current article available.

The previous release of the CRM Connector for GP did not permit installation on a domain which had a ‘-‘ in its domain name. This release addresses this issue.

921020

In the previous release of the CRM Connector for GP, if the date on the computer is in the format dd/mm/yy, when you try to submit an order in Microsoft Dynamics CRM 3.0 by using CRM Connector for GP, you receive the following error message:

The Order submission/update failed. Please try again later or contact your system administrator for details. This release addresses this issue.

923437, 924581

Data is lost when you accept the default system mappings between Microsoft Dynamics CRM and Microsoft Dynamics GP in the Microsoft Dynamics CRM Connector for Microsoft Dynamics GP.

Setup Issues

Microsoft Dynamics CRM Connector for Microsoft Dynamics GP setup stops responding

This can occur if Microsoft Great Plains and Axapta 4.0 are installed on the same computer running SQL Server. You cannot install Microsoft Dynamics CRM Connector for Microsoft Dynamics GP in this configuration.

Microsoft Dynamics CRM Connector for Microsoft Dynamics GP does not support different time zones or time formats

Microsoft Dynamics CRM Connector for Microsoft Dynamics GP does not function if the time zones for Microsoft CRM, Microsoft GP, and the Integration servers are in different time zones or have different time formats. Set all of the time zones and time formats to match.

1.      On the Start Menu, click Control Panel.

2.      Open Regional and Language Settings or the equivalent.

Data Entry Issues

Default Values are not populated in Microsoft CRM orders and invoices

 

When a user adds a line item in a Microsoft GP SOP document, Microsoft GP saves the header document. A SOP message is generated and a corresponding Microsoft CRM Order or Invoice is created with default values. Subsequently, when the user saves the Microsoft GP SOP document by clicking the Save button in Microsoft GP, the Microsoft CRM order or invoice is updated and the default values are lost. The default values will need to be re-entered manually.

This is intermittent but frequent.

 

“Access Denied” error in Microsoft CRM while submitting orders

If Microsoft Dynamics CRM displays an “Access Denied” error while you are submitting an order, the issue may be that you have not set up COM+ Applications with the appropriate permissions.

 

1.  On the Start menu, open the Control Panel.

2.  Open Administrative Tools.

3.  Open Component Services.

4.  Expand the Component Services node, and then expand the Computers node.

5.  Right-click My Computer, and then click Properties.

6.  On the COM Security tab, under Access Permissions, click Edit Default and select the Allow check boxes for Local Access and Remote Access for the affected users, and then click OK.

7.   On the COM Security tab, under Launch Permissions, click Edit Default. Select the group or user names affected, select the Allow check boxes, and then click OK.

8.  Click OK to close the remaining dialog boxes.

9.  Restart Microsoft Distributed Transaction Coordinator.

 

 

Deleting a Microsoft CRM account that is a parent account of another Microsoft CRM contact

 

If a Microsoft CRM account, which is also used as parent account of any other Microsoft CRM contact, is deleted, then the subordinate Microsoft CRM contact will be deleted, but its corresponding Microsoft GP customer will not be deleted.

 

Any updates to the Microsoft GP customer will cause a failure to display in the Integration Monitor tool. To resolve this issue, contact support.

 

Commissions are not calculated for orders that are owned by Microsoft CRM users 

 

If a Microsoft CRM user is mapped to a Microsoft GP Sales Person ID and that Microsoft CRM user creates an order in Microsoft CRM, the Calculated Commission is not calculated.

 

You can update your mapping so that the commissions are calculated.

 

1.      In the connector, open the BizTalk map for the Microsoft CRM Sales Order Detail to the Microsoft GP SOP Line item.

2.      Set the CREATECOMM Flag value to 1.

3.      Redeploy the map. For redeployment instructions, see the Microsoft Dynamics CRM Connector for Microsoft Dynamics GP Guide, Chapter 8: Customizing Integration.

 

Primary Address is required in Microsoft GP if you are using the Sales Person ID, Territory ID, and Country Code to synchronize with Microsoft CRM

 

If a record in Microsoft GP contains data for the Sales Person ID, Territory ID, and Country Code, but does not contain a primary address, and the record is updated in Microsoft CRM, data contained in these three fields in Microsoft GP will be removed.

 

To resolve this, verify that all records in Microsoft GP that contain Sales Person ID, Territory ID, and Country Code also contain a primary address prior to synchronizing Microsoft CRM and Microsoft GP.

Cannot update orders in Microsoft CRM after they are submitted to Microsoft Great Plains

The connector no longer supports updating orders in Microsoft Dynamics CRM submitted to Microsoft Great Plains, write in products, or line items shipped to different locations.

You cannot set the “Send e-mail statements” option in Microsoft GP for an account that was created in Microsoft CRM with an e-mail address

If you want to use the “Send e-mail statement option” in Microsoft GP, you must set the path to the Email Statements Status report in the dex.ini file in Microsoft GP. For example:

EmailStmtStatusPath=C:\Program Files\Microsoft Business Solutions\Great Plains

If the “Send email statement” option has been set previously in a record in Microsoft GP, this path may have already been set. The path is defined automatically the first time the option is set in a Microsoft GP record.

Discontinuing an item in Microsoft GP deactivates the corresponding product in Microsoft CRM

If an item is discontinued in Microsoft GP, the corresponding product in Microsoft CRM will be deactivated. As soon as a product is made inactive, you cannot add it to an order in Microsoft CRM. If you delete an item in Microsoft GP, the corresponding product in Microsoft CRM will be deleted.

Microsoft CRM workflow can change the state of a submitted order to canceled

After the connector is installed, any orders which have been submitted to Microsoft GP cannot be canceled through Microsoft CRM or by using an assembly created with the Microsoft CRM Software Development Kit (SDK). However, workflow can be set to set the state of a submitted order to canceled. It is recommended that you disable any workflow that changes the state of the orders to canceled.

Microsoft GP KIT items do not appear in the Order Product form in Microsoft CRM

Microsoft CRM does not have unit of measure and quantity as properties of KIT components. This information is passed from Microsoft GP to Microsoft CRM and placed in the Description field of the Order Line Item form. This field is not visible on the Order Product form out-of-box. It is recommended that you customize the Order Product form to include the Description field.

Microsoft GP KIT items do not populate the Product Type field in Microsoft CRM

Microsoft GP KIT items do not populate the Product Type field in Microsoft CRM. Microsoft CRM does not have any corresponding type available.

Data Synchronization and Integration Issues

The Data Synchronization Tool cannot synchronize matched and unmatched records in a single batch

 

In the Data Synchronization Tool, you cannot select match and unmatched records of an entity. If you attempt to synchronize these types of records, only the matching records will be published. Although the message indicates that the entity is already in processing, the unmatched records will not be published.

 

An error message displays indicating that the entity is already in processing while publishing the unmatched records. This message is incorrect. The unmatched records will not be published. If you attempt to synchronize again, the matched records will be published again.

 

It is recommended that you synchronize matched and unmatched records in separate batches.

 

 

System Administration Tool does not update automatically to reflect changes


In Microsoft GP, if you delete the default shipping type, payment term, and class ID, the Settings and Administration Tool does not updated automatically to reflect the deletions in Microsoft CRM.

 

After deleting the default shipping type, payment term, and class ID in Microsoft GP, refresh the Settings and Administration Tool before synchronizing Microsoft Dynamics CRM and Microsoft GP.

 

1.  On the Start menu, click All Programs, point to Microsoft CRM Connector for GP, and then click MSCRM Integration, and then click Settings and Administration Tool.

2.   Under  Settings, click Microsoft Great Plains, and then on the File menu, click Refresh.

3.  On the File menu, click Save.

4.  On the File menu, click Close to close the Settings and Administration Tool.

The Microsoft Integration Monitor displays the following messages:

·        BillToAddressKey does not exist.

·        ShipToAddress Key does not exist.

 

There are two reasons that these messages might display:

 

·    In Microsoft Dynamics CRM, the secondary address information from an account or contact was deleted before the integrated account or account was deactivated, and then the account or contact was updated.

·    In Microsoft Dynamics CRM, two accounts or contacts were merged and the subordinate account or record has additional addresses in the “ship to” or “bill to” addresses.

 

To correct these issues, edit the Microsoft CRM Customer Card to clear the addresses in the “Ship to”, “Bill To”, and “Statement To” fields for the corresponding subordinate customer. Future updates will be processed from Microsoft Dynamics CRM to Microsoft GP for the subordinate Microsoft CRM account or customer.

 

Address fields and Address types do not update

 

Updating the ShipTo, BillTo, and StatementTo fields in a Microsoft GP customer card will not change the address type in Microsoft CRM addresses. Customer updates in Microsoft GP will not trigger address updates in Microsoft CRM. This is a technical limitation.

 

Updating the Address Type fields in the Address form in Microsoft CRM will not update the ShipTo, BillTo, and StatementTo fields of a customer entity in Microsoft GP. Address updates in Microsoft CRM will not trigger customer updates in Microsoft GP. This is a technical limitation.

Restoring default settings in the Setting and Administration Tool can cause duplicate entities to be created

In the Settings and Administration tool, you can inadvertently create duplicate mappings if you delete the out-of-box mappings between entities and then create a new mapping before restoring the default.  Both the original mapping and the new mapping are enabled for the entity pair and action combination. Two entities in the destination system are created for each entity in the source system.

To remove the duplicate map, you can find and disable any duplicates.

1.      In the Settings and Administration Tool, under Settings, click Integration Server.

2.      On the Customize Maps tab, select the check box for maps, and then point to More Actions, and click Show History. If two versions of the maps are enabled, clear the check box for the duplicate map.

3.      On the File menu, click Save.

For a Microsoft CRM account without addresses, the connector automatically creates a Microsoft GP primary address ID

When a Microsoft CRM account is created without any addresses, two entities are created in Microsoft GP, a customer and an address ID. The address ID is created to ensure that data in the phone field is not lost and the Microsoft CRM Connector for GP assigns the ID the name "Primary" and then links the address ID with Microsoft CRM account record.

If a primary address is added to the Microsoft CRM account, the connector will update the address, but because you cannot change the name of the address ID in Microsoft GP, you cannot change the address name from “Primary.”

For Microsoft CRM accounts without a phone number, the connector automatically creates a Microsoft GP with the Microsoft CRM address ID

If you choose to create a customer address ID based on a phone number and a Microsoft CRM user creates an account or contact record without a phone number, the record will be created in Microsoft GP with an address ID name used in Microsoft CRM.

Toolbar customizations in the Sales Order form cause an error

If the Sales Order element in the Microsoft CRM  isv.config file contains a <toolbar> tag, then Integration setup does not customize the Microsoft CRM order form. The setup completes, but when the Microsoft CRM order page is opened, an error is displayed.

To resolve this issue, after the connector setup is complete, edit the isv.config file so that all customizations are under one <toolbar> node and bring the attributes up to the <button> level.

Additional Issues

For additional known issues, you can search the Microsoft Support Center for issues regarding Microsoft Dynamics CRM integration with Microsoft Great Plains.

 

 

Documentation Feedback

The Microsoft CRM Connector for Microsoft Dynamics GP Documentation Team welcomes your suggestions and comments about the documentation. You can quickly and directly send e-mail feedback to Documentation Feedback. All feedback must be in English. Please note, the Microsoft CRM Connector for Microsoft Dynamics GP Documentation Team does not respond to technical support questions. If you need technical support, see the "Support Resources and Other Help Documentation" topic in Microsoft CRM online Help. Also, the feedback e-mail that you send is not tracked in Microsoft CRM as an activity.

Copyright

Information in this document, including URL and other Internet Web site references, is subject to change without notice.  Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious.  No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.  Complying with all applicable copyright laws is the responsibility of the user.  Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.  Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2006 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, and Outlook are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.