Release Notes Scribe Adapter for Microsoft Dynamics CRM

Transcription

1 Release Notes Scribe Adapter for Microsoft Dynamics CRM Requirements Version 4.3 Release Date March 30, 2009 Scribe Insight 6.5 or later Microsoft Dynamics CRM 3.0, 4.0, or Online If you are using integration templates provided by Scribe, always check to verify that your template is compatible with this updated adapter. You can verify this information by reading the release notes for your template. You can also check release information in OpenMind for up-to-date information. What s new in version 4.3 Version 4.3 of the Scribe Adapter for Microsoft Dynamics CRM focuses primarily on technical alignment with Scribe Insight version 6.5. What s new in version Fixes Version of the Scribe Adapter for Microsoft Dynamics CRM addresses a number of high-priority customer-reported. Ticket Number Description Web Service Timeouts are hardcoded to 100 seconds M2M object only supported with custom objects 2009 Scribe Software Corporation Revision A / 27-Mar-09 1

2 28681 CRM adpater seeks returning Success >1 throws error CRM Adapter does not handle paging when multi record updates has more matches than the defined Batch limit Publisher issue with custom entities across orgs 25556,25868,26232, 26233,26234,26261, 26251,26279 Assign message being sent on updates when OwnerID not being written to What s new in version Fixes Version of the Scribe Adapter for Microsoft Dynamics CRM focuses primarily on technical alignment with Scribe Insight version 6.4. Technical changes include adding strong naming ( to the adapter. Ticket Number Description 6427 No data for alldayevent field in activity object causes unhandled exception in CRM Conditional Update Using CRM Adapter Issues with Run As User when context changes Installed new CRM adapter - name fields are not populating Danish Version of CRM - Problem on Status/State Code Values , 22088, 24208, , Memory Leak. CRM PlugIn publisher does not publish custom object deletes MSCRMSoapException wrapper class casts incorrectly changing a helpful error message to an unhelpful one. for Microsoft Dynamics CRM 2

3 What s new in version Fixes Uninstalling the adapter After installing the adapter, the adapter now appears in the list of installed programs in Add or Remove Programs in Control Panel. Correct handling of null data When Allow NULL values to overwrite target data was checked, a null value in a DATETIME field in one row would cause a null value to overwrite target data for that field for each succeeding row of source data processed. This issue has been fixed. Case Publishing sales orders An issue introduced in version 4.2 of the adapter would not publish sales orders that were submitted with a SetStateDynamicEntity type of message from the Microsoft Dynamics CRM server. This issue has been fixed. State code changes on sales orders The adapter now creates a sales order in the Submitted state when logging in as the INTEGRATION user. Case Publishing cancelled sales orders The publisher now publishes a message when a sales order is cancelled. Multiple messages from one publisher object The publisher was modified to prevent multiple messages for a single published object. In some cases where there were multiple instances of an object on the published object list, multiple messages would be created for a single instance of the object. This issue has been fixed. DynamicEntityArrayProperties now initialize correctly The adapter now correctly initializes objects with DynamicEntityArrayProperties to eliminate the Unknown property type when creating the Property Setter message. The DynamicEntityArrayProperties designate the members, or entities, in a group (or array). for Microsoft Dynamics CRM 3

4 This defect affected adapter objects that contained dynamic entity arrays, such as the To field on an type of activity. Handling non-us date formats The adapter now properly handles non-us date formats without producing the value is outside the supported range message. Case Microsoft Dynamics CRM server components When installing the Scribe adapter components on a Microsoft Dynamics CRM 3.0 server, the installation path is no longer required to be C:\Program Files\Microsoft Dynamics CRM. Users can now specify the installation path. Case What s new in version 4.2 Workflow publisher for Dynamics CRM Online The adapter includes a new type of publisher that works with Microsoft Dynamics CRM Online. This type of publisher uses Microsoft Dynamics CRM workflows to capture events. The publisher process on the Scribe server polls the Microsoft Dynamics CRM server, reading the Scriberelated events in the System Jobs list and turning them into messages in the ScribeIn message queue on the Scribe server. Designed to be used with Microsoft Dynamics CRM Online, the workflow publisher also works with Microsoft Dynamics CRM 4.0 installed onpremise or with partner hosted Microsoft Dynamics CRM. If you want to publish data from Microsoft Dynamics CRM servers installed on a 64-bit operating system, you must use the workflow publisher. Plug-in publisher for Microsoft Dynamics CRM 4.0 The adapter includes a new type of publisher designed specifically to work with the latest Microsoft Dynamics CRM 4.0 technology. This type of publisher uses a Microsoft Dynamics CRM plug-in to capture events. The plug-in captures events and notifies the publisher process on the Scribe server, which then places the final messages in the ScribeIn message queue on the Scribe server. The plug-in publisher features support for multi-tenant Microsoft Dynamics CRM and requires no manual installation steps on your Microsoft Dynamics CRM. for Microsoft Dynamics CRM 4

5 To upload the publisher's plug-in.dll to the Microsoft Dynamics CRM server, the user must be logged in using Active Directory authentication and be a Deployment Administrator. Set up Deployment Administrators using the Microsoft Dynamics CRM Deployment Manager. Many-to-many relationship support Microsoft Dynamics CRM 4.0 includes more flexible entity relationships including the ability to create custom many-to-many relationships. New many-to-many relationships are handled by custom entities in the Microsoft Dynamics CRM system. The Scribe Adapter for Microsoft Dynamics CRM exposes these custom entities, so you can create and remove relationships between records in Microsoft Dynamics CRM. For more information, see Working with many-to-many relationships in the Reference section of the adapter s Help. Forms authentication The adapter supports the new forms-based authentication method introduced with Microsoft Dynamics CRM 4.0. New connection dialog box After you choose your Microsoft Dynamics CRM version, a new connection dialog box prompts you only for information needed for that version to connect. Fixes New Help Easy to follow step-by-step instructions for common tasks. Includes installation, set up, and testing instructions - everything you need to get the adapter up and running. Decimal field rounding The adapter now correctly rounds decimal fields. Case Query publishers with filters now return data A query publisher with a filter that is connected to the Scribe Adapter for Microsoft Dynamics CRM now returns data and publishes a message. Case for Microsoft Dynamics CRM 5

6 Adapter limitations Company match component not supported for Microsoft Dynamics 4.0 The company match component is now supported for Microsoft Dynamics CRM 3.0 only. If you are using that component and you upgrade your Microsoft Dynamics CRM 3.0 server to Microsoft Dynamics CRM 4.0, you will need to change the lookup links on any DTS files that use the new_scribe_stripcompany custom attribute that is part of company match. For instructions on replacing the lookup link see step 8 of the upgrade instructions, below. Known issues Case Number Description Issues in CRM when trying to publish Discount entity. A fix for this issue will be considered in a future release. CRM adapter publisher reconnect required to upgrade the Plug-in publisher on the CRM server To upgrade from the CRM Callout Publisher Use these instructions if you are for upgrading from Microsoft Dynamics CRM 3.0 or earlier and using the CRM callout publisher. 1. Back up your data. If you are using, Microsoft Dynamics CRM 4.0. Back up your SCRIBEINTERNAL database and Microsoft Dynamics CRM databases. Microsoft Dynamics CRM 3.0. Back up your SCRIBEINTERNAL database and callout.config.xml (typically located on your Microsoft Dynamics CRM server under \Program Files\Microsoft Dynamics CRM\ Server\bin\assembly). 2. If you are using the callout publisher with, Microsoft Dynamics CRM 3.0 server. Continue using the callout publisher. Skip to step 6. Microsoft Dynamics CRM 4.0 server. Remove the callout publisher components from the Microsoft Dynamics CRM 4.0 server and start using the plug-in publisher (follow the lettered steps below). for Microsoft Dynamics CRM 6

7 a. On the Microsoft Dynamics CRM 4.0 server, remove the Scribe Configuration Utility for Microsoft Dynamics CRM Server. Open Windows Control Panel and open Add or Remove Programs. Click Scribe Adapter for Microsoft Dynamics CRM 4.x CRM Server Components. Click Change/Remove. b. When removing the program is complete, open Windows Explorer and browse to C:\Program Files\Microsoft Dynamics CRM\Server\bin\assembly. c. Delete the file Scribe.MSCRMAdapter30.CalloutComp.dll. In Control Panel, click Administration Tools, click Computer Management. In the Computer Management window, click Services and Applications, click Internet Information Services (IIS) Manager. Double-click Application Pools. Right-click on CRMAppPool, on the shortcut menu, click Stop. You should now be able to delete the file Scribe.MSCRMAdapter30.CalloutComp.dll. 3. If you are running the Scribe Insight server and the Microsoft Dynamics CRM server on the same computer, follow the lettered steps, below; otherwise skip this step. a. In Control Panel, click Add or Remove Programs. b. Click Scribe Insight. c. Click Remove. This opens the Scribe Insight Installation Wizard. d. In the Installation Wizard, choose Repair and click Next. e. Click Install. f. Click Finish. 4. Remove the references to Scribe-related callouts from the callout configuration file, callout.config.xml. Be careful when editing the callout configuration file as it contains references to all callouts, including those not related to Scribe. Scribe recommends backing up the callout configuration file or managing it through some type of version control. a. Use Windows Explorer to browse to C:\Program Files\Microsoft Dynamics CRM\Server\bin\assembly. b. Open the file callout.config.xml in a text editor (such as Notepad). for Microsoft Dynamics CRM 7

8 c. Locate the callout elements that are related to Scribe. Those elements will have a child subscription assembly equal to Scribe.MSCRMAdapter30.CalloutComp.dll. Example, <callout entity= account event= PostUpdate > <subscription assembly= Scribe.MSCRMAdapter30.CalloutComp.dll class= Scribe.MSCRMAdapter30.CalloutComp.CalloutComponent > <prevalue>@all</prevalue> <postvalue>@all</postvalue> </subscription> </callout> d. Delete each Scribe-related callout element - including the opening <callout> tag, the closing </callout> tag, and everything in between the tags. e. Save the callout.config.xml file. f. In Control Panel, click Administration Tools, click Computer Management. g. In the Computer Management window, click Services and Applications, click Internet Information Services (IIS) Manager. h. Double-click Application Pools. i. Right-click CRMAppPool, on the shortcut menu, click Start. j. Restart IIS. 5. Connect the plug-in publisher to your Microsoft Dynamics CRM server. a. In the Scribe Console, open Properties for the Publisher for Microsoft Dynamics CRM. b. Click Step 4 Publisher/Bridge Properties. c. Click Settings and enter the login properties for your Microsoft Dynamics CRM server. d. Click OK to save your settings. e. Click Step 5 Activation and then click Apply. 6. If you were using the company match component, edit your DTS files to change the lookup links that used the new_scribe_stripcompany custom attribute that is part of company match. Replace that lookup link with a new lookup link on the account name that uses the STRIPCOMPANSUFFIX() function and the Starts With operator. for Microsoft Dynamics CRM 8

9 Feedback While this is not an exact equivalent for company match capability, it is a reasonable replacement for doing fuzzy account name matching. Scribe is very interested in hearing about your experiences with our products and documentation. We welcome your suggestions for improvement and encourage you to use the Scribe OpenMind community at to provide feedback. OpenMind also lets you see information on upcoming product releases and engage in online discussions with Scribe product management and other Scribe users. Request a logon at - end - for Microsoft Dynamics CRM 9