Microsoft Dynamics 365 / CRM Release Notes

Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.

See TIBCO Scribe® Online Connector For Microsoft Dynamics 365 / CRM for more information.

Note: To access any changes to metadata support, such as new operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata.

Version 1.11.1

Released April 15, 2021.

New And Noteworthy

A new Connection String deployment type has been added to the Connection dialog to create custom Connection Strings for the following Authentication types: (SCMSCRM-610)

Changes in Functionality

The Discovery URL field has been removed from the Connection dialog because Microsoft has retired this service. In addition, WS-Trust used by the Partner-Hosted (IFD) deployment option is being retired.(SCMSCRM-610)

Note: Use of regional discovery services is being retired by Microsoft in the very near future. This means that the Online Deployment option will no longer work. In addition, Microsoft has announced that it will retire the use of Office 365 credentials in April 2022. See this Microsoft Notification. Best practice is to use Azure AD instead. The Online option will be removed from the User Interface in a future release.

Note: Microsoft is deprecating WS-Trust. This means that the Partner-Hosted (IFD) deployment option will no longer work. See this Microsoft Notification. Best practice is to move to the Connection String deployment type before April 2022. The Partner-Hosted (IFD) option will be removed from the User Interface in a future release.

Known Issues

SCMSCRM-715

Summary: When creating an account that includes a reference to a custom parent lookup object, errors similar to the following are generated: (Case # 01950851)

Operation failed. Label: Create account, Name: accountCreate, Message: -2147220989:Required member 'LogicalName' missing for field 'Target'

Workaround: Contact Support for hotfix SCMSCRM-696.

SCMSCRM-709

Summary: The Audit entity displays in the Create target operation even though it does not support Create. This is a read-only entity. (Case # 02046825)

Workaround: None.

SCMSCRM-708

Summary: Querying the Audit entity sometimes generates PagingCookie errors similar to the following: (Case # 01951584, 01952323, 02041396, 02041751, 02042092, 02042163, 02044658, 02045680, 02046341)

Unable to get the next page of data. Dynamics 365 has not advanced the page cookie for Entity:audit

Workaround: Contact Support for hotfix SCMSCRM-697.

SCMSCRM-706

Summary: In some cases, when batch processing is enabled the connector is not using multiple threads during runtime. (Case # 01945353, 01949573, 02038495, 02043669, 02044083)

Workaround: Contact Support for hotfix SCMSCRM-700.

SCMSCRM-704

Summary: The Run As user used for Net Change is not set correctly for new authentication types supported for this connector, which prevents Net Change from being used. (Case # 01951143, 01950603)

Workaround: Contact Support for hotfix SCMSCRM-693.

SCMSCRM-694

Summary: The Query block returns an incorrect value for the Audit entity "objecttypecode" field. (Case # 01927764)

Workaround: Contact Support for hotfix SCMSCRM-617.

SCMSCRM-395

Summary: Some entities that should not be available to be selected in Replication Solutions are displayed in the Selected Entities list. (Case # 01821017, 01821631, 01821316, 01821008, 01820963)

Workaround: Review the Microsoft Dynamics 365 Entities Not Included In Recommended Or Selected Lists table in the Help for a list of entities that should not display and should not be selected.

SCMSCRM-390

Summary: When working with the Email entity and the associated activitymimeattachment child entity, if you use a For Each Child Block to create an attachment that references a file name and not the full path, an error similar to the following is generated: (Case # 01813760)

"Operation failed. Label: Create Note, Name: annotationCreate, Message: 2:The following error has occurred: Could not find file 'C:\Windows\system32\RDEB6806610.24.19.pdf"

Workaround: Use a Fetch Block instead of a For Each Child Block to retrieve the child records.

SCMSCRM-295 / SCMSCRM-6

Summary: The salesprocessinstance entity is not supported but may display in the available entities when configuring a Replication Solution using Selected Entities or an Integration Solution Query Block. Attempting to use this entity in a Solution generates errors similar to the following: (Case # 01748844)

ERROR: Exception Type : InvalidExecuteQueryException

Message : The following error has occurred in the Dynamics 365 Connector: Sql error: Generic SQL error. CRM ErrorCode: -2147204784 Sql ErrorCode: -2146232060 Sql Number: 207
The following error has occurred in the Dynamics 365 Connector: Sql error: 'Invalid column name 'ImportSequenceNumber'. Invalid column name 'TimeZoneRuleVersionNumber'. Invalid column name 'Name'. Invalid column name 'OverriddenCreatedOn'. Invalid column name 'UTCConversionTimeZoneCode'.': Error in call to child Process

Workaround: Do not select the salesprocessinstance entity in Replication or Integration Solutions.

68058

Summary: The UserSettings entity is not available in the metadata for the Microsoft Dynamics 365 / CRM Connector. (Case # 66152, 01726282) .

Workaround: Try using Native Query to retrieve the entity.

65942 / SCMSCRM-56

Summary: The CalendarRule entity is not available in the Selected Entities option for Replication Solutions nor is it available for Integration Solutions. It is included in the Recommended Entities option for Replication Solutions. (Case # 65389, 01725537)

Workaround: For Replication Solutions, use the Recommended Entities option.

65147 / 65946 / SCMSCRM-38

Summary: Related entity aliases longer than 128 characters are not supported in the Query Block Include tab and, if selected, generate errors similar to the following: (Case # 64849, 01725003)

Message: ExecuteQueryCommandHandler - Exception : Exception Type : InvalidExecuteQueryException

Message : The following error has occurred in the Dynamics 365 Connector: Alias length cannot be greater than 128

Workaround: None.

51830

Summary: NULL values in either a LOOKUPTABLEVALUE formula or a Lookup Table cause the Map to skip the subsequent operation block. (Case # 61062, 01721389)

Workaround: Use the IFNULLUSE function to check for NULL values.

39764

Summary: In some cases executing a Map with Batch Processing configured for a large batch size, such as 3000, causes errors and stops executing. (Case # 57185, 01717744)

Workaround: Reduce the batch size and run the Map again.

38469 / SCMSCRM-106

Summary: Querying internal use only entities, such as systemusermanagemap, in an Integration Solution generates errors similar to the following: (Case # 55890, 01716529) 

The 'RetrieveMultiple' method does not support entities of type 'systemusermanagermap'.

Workaround: Use a Replication Solution instead.

Version 1.10.1

Released February 23, 2021.

New And Noteworthy

This release of the Microsoft Dynamics 365 / CRM Connector was built against version 9.0.45.3930 of the Microsoft Dynamics 365 SDK.

SCMSCRM-457

Enabled the display name for the two option datatype instead of only returning the numeric value. (Case # 01888706)

Changes In Functionality

SCMSCRM-459

Microsoft is deprecating the following Microsoft Dynamics 365 services:

Connections To Existing Microsoft Dynamics 365 Organizations

If you have Microsoft Dynamics 365 / CRM Connections to existing Microsoft Dynamics 365 Organizations or Customer Engagement Trials configured in TIBCO Scribe® Online, they will continue to work until February 2021. Best practice is to update those Connections to use Azure AD authentication.

Connections To New Microsoft Dynamics 365 Organizations

The Online Deployment option on the Microsoft Dynamics 365 / CRM Connection dialog is not supported for new Microsoft Dynamics 365 Organizations or Customer Engagement Trials. Use the Azure AD option instead.

Closed Issues

SCMSCRM-585

Removed the virtualresourcegroupresource entity from the list of Recommended Entities for Replication Solutions. (Case # 01898435, 01901816)

SCMSCRM-572

Updated the validation for the Upsert operation to conform to the latest changes to the Microsoft Dynamics 365 SDK, which addresses errors similar to the following: Message: -2147088240:The specified key attributes are not a defined key for the XXX entity. (Case # 01897163, 01897446)

SCMSCRM-460

Enabling Batch Processing on Upsert operations caused Statecode and Statuscodes to be set to default values for inserted records. (Case # 01821055)

SCMSCRM-455

New Azure Data Lake entities, datalakeworkspace and datalakeworkspacepermission, are not accessible in Replication Solutions and generate errors when selected. These two entities have been removed from the list of recommended entities. (Case # 01885993, 01885968, 01886125)

SCMSCRM-383

The Connector was unable to access custom N:N related entities. (Case # 01805759, 01805720, 01806408, 01806635, 01806906, 01807008, 01807190, 01807350, 01807414)

Version 1.8.1

Released October 4, 2019.

New And Noteworthy

Migration And Compatibility

Replication Solutions Net Change Filters

64825 / 72377 / SCMSCRM-61

When a group of changes was written to Microsoft Dynamics 365 / CRM all at the same time, only a portion of them were returned by a subsequent query because the Microsoft Dynamics 365 / CRM datetimestamp did not include milliseconds. When a subsequent Replication Solution executed and was using Net Change to filter for new and updated records, some records were not included in the replication. (Case # 64903, 66502, 01726628, 01727993)

For example, assume the last record written before the Replication Solution completed had a modifiedon date of 09/04/2018 10:10:20 and the next Replication started with data that had a modifiedon date of 09/04/2018 10:10:21. Any records that arrived between the end of the Replication Solution and 09/04/2018 10:10:21 were not included because milliseconds were not used as part of the filter.

Important Note: To alleviate this issue, the Microsoft Dynamics 365 / CRM Connector now subtracts a second from the most recent modifiedon date to ensure that no records are missed. This could cause a few records to be reprocessed. For example, if the last record written had a modifiedon date of 09/04/2018 10:10:20, the next Replication starts with data that has a modifiedon date of 09/04/2018 10:10:19. Any records that were already processed between 09/04/2018 10:10:19 and 09/04/2018 10:10:20 are processed again.

Changes To Recommended Entities For Replication Solutions

The production version of the Microsoft Dynamics 365 / CRM Connector has a preset list of Recommended Entities that can be used when configuring a Replication Solution. To improve performance and prevent errors, the list of Recommended Entities is being modified.

Note: To continue replicating an entity that has been removed from the Recommended Entities list, configure a second Replication Solution with Selected Entities and specifically choose the entities you need. Both Solutions can replicate to the same target datastore.

After the Connector update, you may see error messages for existing Microsoft Dynamics 365 / CRM Replication Solutions that are set to replicate Recommended Entities. To take care of the errors and access the new list of Recommended Entities, you must do the following:

  1. Reset metadata for your Microsoft Dynamics 365 / CRM Connections.
  2. Open any Replication Solutions that use Microsoft Dynamics 365 / CRM as a source and replicate Recommended Entities.
  3. Change the Entities selection on the Solution to either All entities or Selected entities.
  4. Allow the Solution to save and finish preparing.
  5. Change the Entities selection on the Solution back to Recommended Entities.

After the update, if you have not reset metadata and modified your Replication Solutions as listed above:

Note: See the Updates To TIBCO Scribe® Online Connector for Microsoft Dynamics 365 / CRM Replication Solutions Knowledge Base article for the list of entities that have been removed from the Recommended Entities list.

Closed Issues

SCMSCRM-294

Added support for the FetchXML top attribute to return the top x number of records in a set of query results. This attribute has a limit of 5000 records. (Case # 01788925)

68432 / SCMSCRM-240

In some cases using FetchXML in the Native Query Block returned null values in fields for related entities. (Case # 66530, 01726656, 01767672, 01775396)

69757 / 73952 / SCMSCRM-69

When connecting to Microsoft Dynamics 365 / CRM V9.0 and, creating a Campaign Response only the Regarding and Owner Activity Party records were created, but not the Customer Activity Party record. (Case # 67258, 01727383)

73236 / 73458 / SCMSCRM-65

For the Opportunity entity, the Microsoft Dynamics 365 / CRM schema did not contain both the GUID and the logical name for parentaccountid and parentcontactid. Both are required when creating an Opportunity. An error similar to the following was generated: (Case # 68865, 68943, 68998, 69234, 69236, 01728985, 01729063, 01729118, 01729354, 01729356, 01729736, 01730038, 01730306, 01730351, 01730503, 01757529, 01762998)

Attribute customeridtype must not be NULL if attribute customerid is not NULL

75228 / SCMSCRM-57

Using the sharepointdata entity in an Integration Solution Query or in a Replication Solution Selected Entities list generated errors similar to the following: 'Invalid column name 'PageNumber' (Case # 69954, 01730073)

61210 / 65174 / 69545 / 70142 / 73803 / 74128 / 74456 / SCMSCRM-43 / SCMSCRM-47 / SCMSCRM-51 / SCMSCRM-239

The default list of recommended entities used for Replication Solutions included some unnecessary entities that generated errors. Those entities have been removed from the list. (Case # 40998, 64075, 64246, 64287, 64537, 65146, 67133, 67134, 68033, 68473, 69217, 69463, 01715465, 01724231, 01724402, 01724443, 01724636, 01724693, 01725294,01727259, 01727260, 01728154, 01728593, 01729337, 01729727, 01729583, 01730168, 01730204)

66478 / 67597 / 69918 / SCMSCRM-39

Unable to process query results when an unsolicited relationship was returned in the query request. ( Case # 65231, 01725379)

57148 / 57803 / 61379 / 63170 / SCMSCRM-4

Using more than one Order by function in Fetch XML in a Native Query block sometimes generated paging errors. (Case # 62334, 01722605, 01730451, 1730470)

75508 / 75655 / SCMSCRM-11

When the virtual entity msdyn_componentlayer was present in a Microsoft Dynamics 365 / CRM Organization, selecting the Recommended Entities option for a Replication Solution generated errors similar to the following: Error in call to child Process (Case # 70235, 70321, 70330, 70340, 70402, 01730353, 01730439, 01730448, 01730458, 01730520)

SCMSCRM-8

The Microsoft Dynamics 365 / CRM Connector generated paging cookie errors on the msdyn_solutioncomponentsummary entity when replicating all entities. (Case # 1748845)

SCMSCRM-5

Excluded the rollupjob entity from the list of entities that can be replicated. (Case # 1732179)

SCMSCRM-3

Updated Microsoft Dynamics 365 / CRM Connector Help to indicate that deletes are not recorded for the activitypointer entity. This affects Replication Solutions and prevents the deleted records from being removed from the target datastore. To work around this issue you can delete the entire activitypointer table from the target datastore and run the Replication Solution again to recreate the table. (Case # 01731612)

Version 1.7.1

Released November 26, 2018.

New And Noteworthy

Closed Issues

57183 / 68811

Solutions containing Lookup or Fetch Blocks with a large number of fields sometimes generated 'System.OutOfMemoryException” errors. (Case # 61760, 66648)

Version 1.6.2

Released July 2, 2018.

New And Noteworthy

There are no new features in this release.

Closed Issues

66639 / 66821

Merge and Execute Blocks did not display in the palette when editing a Map with a Microsoft Dynamics 365 / CRM Connection. (Case # 65928, 65842, 66287)

Version 1.6.1

Released April 18, 2018.

New And Noteworthy

There are no new features in this release.

Closed Issues

14415

In the recent Connector For Microsoft Dynamics 365 / CRM release, the Connector was modified to allow leading and trailing spaces in string field values for filters, lookup criteria, match criteria, and target operations. This change caused errors or duplicate records in some existing integrations because the new field values with spaces did not match the existing field values in the target. To prevent further issues, an update was released to return the Connector to its prior state and trim leading and trailing spaces from string field values. (Case # 65172, 65178)

Version 1.6.0

Released April 16, 2018.

New And Noteworthy

Closed Issues

11317

Disabled Batch Processing for CalendarRule and ActivityParty entities to ensure that both parent and child records are successfully written to Microsoft Dynamics 365 / CRM and prevent an erroneous successful record count in Execution History. (Case # 52871)

14415

Leading spaces were removed from field values when creating an address in Microsoft Dynamics 365. (Case # 79374)

30717

Using a Query, Fetch, or Lookup Block to access a record with a money data type field when Agent debug was enabled, generated errors similar to the following: (Case # 85649)

"Operation failed.  Label: Fetch Invoice Details, Name: invoicedetailFetch, 
Message: Type 'Microsoft.Xrm.Sdk.Money' with data contract name

57663

Creating a System User and assigning that user to a Business Unit generated errors similar to the following: (Case # 62633)

Message: The following error has occurred in the Dynamics 365 Connector: 
System.Exception: Invalid Set Business User Request

61744 / SCMSCRM-5

Excluded the internal entities listed below from the Recommended and Selected entity lists for Replication Solutions. If necessary, these entities can be replicated by selecting the All Entities option. (Case # 40998, 63587, 1732179)

Note: If you are connecting to Microsoft Dynamics 365 version 9.0 and you are using Replication Solutions with the Recommended Entities option enabled, you may encounter an error.

For Cloud Services, contact Scribe Support.

For On-Premise Agents, follow the steps below to resolve the error.

  1. On the server where your TIBCO Scribe® Online Agent is installed, navigate to the Agent folder and delete the metadata file. Typically, the path and file name are similar to the following:

    C:\Program Files (x86)\Scribe Software\TIBCO Scribe® Online Agent\Connectors\Scribe.Adapter.Crm\Metadata_167207926

  2. In TIBCO Scribe® Online, select More > Connections.
  3. Locate your Microsoft Dynamics 365 / CRM Connection and select Reset Metadata from the Gear menu.
  4. Open your Microsoft Dynamics 365 / CRM Replication Solution and choose All Entities.
  5. When the Solution is done Preparing, choose Recommended Entities again. The entities listed above are now excluded from the list of Recommended Entities.
  6. When the Solution is done Preparing, it is ready to execute again.

Version 1.5.1

Released November 28, 2017.

New And Noteworthy

There are no new features in this release.

Closed Issues

50278 / 52173 / 52462

Replication Solutions now use the CreatedOn datetime field in the Dynamics 365 scribechangehistory custom entity to determine when a record has been deleted and updates the Scribe_DeletedOn field for the corresponding record in the target datastore. (Case # 60654)

54415 / 54516 / 54520

When multiple Solutions made metadata requests while the cached metadata was being updated, the Solutions stopped executing with a Fatal error similar to the following: Fatal Error: The wait completed due to an abandoned mutex (Case # 61923)

Version 1.5.0

Released October 11, 2017.

New And Noteworthy

Closed Issues

48219

When more than one record matched the Matching Criteria for an Update operation, the error message returned was different when Batch Processing was enabled or disabled, even though the root cause was the same. (Case # 59826)

49446 / 49678

Replication Services Solutions attempted to replicate unreadable fields for some entities causing the replication to end with 0 records processed. (Case # 60297)

Version 1.4.0

Released May 2, 2017.

New And Noteworthy

Closed Issues

31908 / 34642

Added support for custom fields of type customer and customeridtype customerid, which resolves the following error that occurred when trying to update field xxx_customerid: Attribute xxx_customerididtype must not be NULL if attribute xxx_customerid is not NULL. (Case # 52352) Refer to the Id And Idtype section of the help for an example of how to map fields that are dependent on each other.

33267

Fixed a paging issue when integrating large numbers of parent/child records into a target datastore where the execution stopped after processing approximately 1000 records and no error was generated. (Case # 89086)

33985

When using a GUID as match criteria for an Update/Insert operation, if there was no matching record, the Insert operation did not complete and the Map failed. (Case # 89099)

33998

Enabling Batch Processing on target operations caused timeout errors when processing a large number of records. (Case # 89235, 88959)

34008

Updating Dynamics 365 with NULL values using the primary key as the match criteria was unsuccessful and the original value was retained. (Cases # 89143)

34500

Mapping the primary key in an Update operation generated the following error: (Case # 54958)

Cannot insert duplicate key.

39367

Added support for date/time fields values as early as 1/1/1753. (Case # 57218)

40630

For Replication Solutions, deleted records were not being purged from the target datastore after 60 days. (Case # 56502)

Winter 2015 Release

New And Noteworthy

Validated support for Dynamics CRM 2015.

Closed Issues

There are no closed issues in this release.

October 2014 Release

New And Noteworthy

Added a Home Realm URL field to the Dynamics 365 connection dialog that allows you to define the URL of a third party authentication server when Partner-Hosted (IFD) is selected. This field is optional.

Closed Issues

9082 / 9083

The Dynamics 365 Connector locked the SQL database during integration. (Case # 62583)

July 2014 Release

New And Noteworthy

TIBCO Scribe® Online Connector for Microsoft Dynamics 365 / CRM has been validated against the MS Dynamics CRM 2013 SP1 (Spring 2014) release.

Closed Issues

7067

For TIBCO Scribe® Online Replication Solutions, timezonerule and timezonedefinition entities were replicated for every run. — After upgrading to Dynamics CRM 2011 Online UR12, a large number of fields were replicated for every TIBCO Scribe® Online Replication Services run. The Dynamics 365 modification date was not changed between the runs, and all of the same entities were duplicated from one run to the next. (Case # 50087)

June 2014 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

8167

Using a Dynamics 365 connection as an Integration Solution source occasionally resulted in the following error: (Case # 54643, 54662, 54949, 55015)

'Paging Cookie And Query Do Not Match'.

8683

User experienced occasional timeout issues when replicating against a Dynamics CRM Online organization. (Case # 59728)

8695

String or binary data would be truncated in metadatadifference table replication (Case # 60154)

Note: Reset the metadata of existing Dynamics 365 connections to effect this change in Replication Solutions.

March 2014 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

8260

ListMember Dynamics 365 entity was not tracking deletes in replication services (Case # 55599).

8294

Query alias name cannot be greater than 128 — When running a solution using Dynamics 365 as a source connection, if you changed the relationship name to one that is longer than 128 characters, you sometimes saw the following runtime error: 

Alias length cannot be greater than 128.

TIBCO Scribe® Online uses the relationship name as the alias for the query and our investigation found a limitation in the Dynamics 365 SDK that does not support query aliases longer than 128 characters. In this scenario, we maintain this limitation and recommend that you do not rename these relationships to names longer than 128 characters.(Case # 55072)

8323

Source option Process Records Based on Modified Date generatee an error (Case # 55249).

October 2013 Release

New And Noteworthy

Dynamics CRM Online and On-Premises 2011 and 2013 are now supported with TIBCO Scribe® Online.

Closed Issues

7886

Paging cookie error was generated when replicating ResourceGroupExpansion entity (Case # 52777)

August 2013 Release

New And Noteworthy

You can now specify a user for Dynamics 365 Connections (the Run As user) that can perform operations as an alternate user.

Closed Issues

6969

Change the Dynamics 365 Connector UI to replace "Windows Live Id" to something more generic such as "Email"

7561

Could not use some Microsoft Dynamics 365 / CRM entities (e.g., Team) in Integration Solution maps be cause they were not-included entities in both Replication Solution and Integration Solution. (Case # 51866)

7668

'Invalid column name' error was generated when running Replication Solutions (Case # 52099)

7678

Could not find mapped Dynamics 365 field in metadata. (Case # 52536)

June 2013 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

7470 / 7469

Users were unable to create an ActivityParty record to relate to CampaignResponse Customer.  (Case # 51594).

April 2013 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

7364

Inserting a picklist value on a custom entity in Dynamics 365 resulted in a serialization error when running the Solution. This is caused by that picklist value being backfilled in its Native CRM type not a standard .NET type. (Case # 50694)

March 2013 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

Replication of Dynamics 365 data source yielded a “Value cannot be null. Parameter name: source” error.

6801

Fixed Replication error of “Failed to insert record, parameter value out of range” for Dynamics 365 currency data types (Case # 49087).

6874

Replication runs for both Salesforce and Dynamics 365 are showing 1 more record processed than what should be for the job.

6931

Process fails sporadically with “Metadata_-634426967.xml' because it was being used by another process” error (Case # 49663).

7043

Fixed Replication error when connecting to CRM 2011 RU12 data source — e.g., “webresource metadata for field is incorrect” (Case # 49965,50075,50077,50079,50164, 50192).

7309

Lowering the precision of a Dynamics 365 entity field (e.g., decimal—currency) which already contained data caused an RS fatal error. (Case # 50889, 50870, 50899)

January 2013 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

6801

Failed to insert record, parameter value out of range. Replication of any currency field with precision of “0” yielded the following error: (Case # 49087)

Failed to insert record: Parameter value '##########.0000" is out of range.

6931

Dynamics 365 Metadata.xml file was being used by another process. Sporadic issue where the same Dynamics 365 connection was used as source or target in multiple Solutions (RS and/or IS) where the user received an error stating that the process cannot access the metadata.xml file because it is being used by another process. (Case # 49663)

7043

Dynamics CRM 2011 webresource metadata for field was incorrect. With Microsoft’s release of Dynamics CRM 2011 RU12, several RS Solutions failed with the following error: ( Case # 49965, 50075, 50077, 50079, 50164, 50192 )

String or binary data would be truncated. The statement has been terminated.

This error occurred for entities including activitymimeattachment, annotation, attachment, webresource, processsession, and salesliteratureitem. The resulting SQL replication table stored an incorrect column size for specific fields in these entities.

November 2012 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

6806

The Replication for Dynamics 365 was missing brackets on the delete statement (Case # 48786)

September 2012 Release

New And Noteworthy

Added support for source queries with parent joins that contain intersect entities, such as listmember.

Closed Issues

There are no closed issues in this release.

July 2012 Release

New And Noteworthy

Closed Issues

6373

CSV files failed to completely process - execution log showed success – When running a CSV to Dynamics 365 Integration Solutions, sometimes the source CSV file was not fully processed. However, the execution history showed it was successful, no errors were logged, but only partial data was processed to the Target Dynamics 365 system. (Case # 46348)

May 2012 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

6220

Users reported that the audit table no longer replicated. Research showed that a phantom attribute ('objecttypecode') was being retrieved for the audit entity, which did not exist in metadata. Since the field was already (incorrectly) retrieved as an attribute of the objected, an error occured and the replication stopped. This issue has been fixed in this release. (Case # 46160)

6248

If you created several Microsoft Dynamics 365 / CRM organizations that shared the same friendly name,TIBCO Scribe® Online could not distinguish between them even though they had different URLs. This issue has been resolved by allowing you to use the unique organization name in Dynamics 365 when configuring the connection, thereby loading the correct metadata for that specific organization. (Case # 46505)

February 2012 Release

New And Noteworthy

Microsoft Dynamics 365 / CRM Connections now support Microsoft Office 365 user IDs.

Closed Issues

When you are defining a Connection to Microsoft Dynamics 365 / CRM, Microsoft now properly handles Organizations with commas in their name when browsing Dynamics 365 organizations (Case # 44773).

Refreshing metadata for an existing Dynamics 365 connection intermittently generated an incorrect secured fault error (Case # 44909).

August 2011 Release

New And Noteworthy

Dynamics 365 Picklist Display Names: TIBCO Scribe® Online Replication Solutions now have the ability to include both the value and the corresponding label/display name of Dynamics 365 optionset fields (or picklists) in replicated tables.

Closed Issues

For Dynamics 365 as source, the ActivityPointer table is no longer replicating and is not even showing in the entity selection screen. (Case # 42434)

Dynamics 365 replication is taking longer than it should and stops running after 8 hours; resulting in the following error: (Case # 42396, 41663, 41645)

“An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.”

For Dynamics 365 as source, Activitymimeattachment table failed to replicate large attachments. Replication failed with the error "Failed to allocate a managed memory buffer of 268435456 bytes. The amount of available memory may be low.". For this example, this entity had a field with the size of 268435456 bytes; resulting in a failed replication. Excluding said table from the entity list allowed for a successful replication. (Case # 42359)

Dynamics 365 entities that had Customer and Owner attribute types were not getting the corresponding 'name' field populated; the fields were instead set to null. Some specific examples are the Opportunity entity (owneridname & customeridname fields) and the Contact entity (parentcustomeridname field). (Case # 42165)

June 2011 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

Error-Free Replication: As was described as a known issue in the May 2011 release notes (May 2011 Update), the TIBCO Scribe® Online RS service was impacted by a bug in the Microsoft API by which the metadata regarding the structure of entities in Microsoft Dynamics CRM 2011 did not match the actual data. This issue resulted in replications regularly reporting row-level failures during execution. Effective with the June 2011 update, replications should generally run without row errors.

Merged Records from Microsoft Dynamics CRM 2011 Online failed to replicate with TIBCO Scribe® Online RS. (Case # 41588)

Fixed issue with ActivityPointer.ActivityTypeCode columns (Case # 41151).

May 2011 Release

New And Noteworthy

Users can now select Partner-Hosted (IFD) deployment in addition to Online and On-Premise. IFD (Internet Facing Deployment), is the typical configuration for Microsoft Dynamics 365 / CRM environments hosted by 3rd party partners.

Closed Issues

Added logic to work around defects in the Microsoft Dynamics CRM 2011 API in which metadata reported by the API does not match the data received by the API. Added some additional logic to work around these issues which results in fewer row errors. For example Goals and ImportLogs should no longer fail..

April 2011 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

Connection information sometimes did not show up correctly in the Edit Connections page in cases when you had multiple CRM connections in your organization.

Renaming an existing CRM connection inadvertently dropped this connection from any Solution that was pointing to it originally.

March 2011 Release

New And Noteworthy

With the release of Microsoft Dynamics CRM 2011 Online, the agent has been updated to use the latest CRM API from Microsoft. Existing users will need to update to the latest agent to take advantage of this feature.

Closed Issues

TIBCO Scribe® Online RS created a custom entity in the CRM account to track deleted items. Non-US CRM 2011 implementations did not support the en-US language code of 1033 when creating the new_scribechangehistory, causing the table to not get created and our process to fail.

If the machine clock where the TIBCO Scribe® Online agent is running was off by a few minutes, user would get a null reference exception when connecting to Dynamics CRM Online.

TIBCO Scribe® Online did not properly handle international data formats (e.g., non-DD/MM/YYYY).

Dynamics 365 connection error messages were difficult to understand. TIBCO Scribe® Online was displaying the exceptions directly from Dynamics CRM. These error messages were often cryptic. TIBCO Scribe® Online now detects these errors, offers a message that is easier to understand for end users, and suggestions on how to resolve the issue.

January 2011 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

Microsoft Dynamics 365 / CRM schema updates were not automatically detected. Microsoft Dynamics 365 / CRM has the ability to indicate when schema-level information has changed. In the August 2011 release of TIBCO Scribe® Online, we added the capability for TIBCO Scribe® Online RS to recognize when a schema change occurred, and update the schema of the target database automatically. With the December 2011 release, the feature was mistakenly removed, requiring you to manually choose to refresh metadata from the Connections page. With this new Agent release, the capability to automatically detect schema changes in Microsoft Dynamics 365 / CRM and update the target schema automatically is restored.

Related Topics

Release Notes And Known Issues