Microsoft Common Data Service (CDS) 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 Common Data Service (CDS) 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.
Note: If you had a Microsoft Dynamics 365 / CRM organization when you created your Microsoft Common Data Service (CDS) database, a subset of the Dynamics 365 entities are included in that database. In this case, any Closed Issues or Known Issues for the Microsoft Dynamics 365 / CRM Connector may apply to the CDS Connector also and are included in this set of release notes.
Version 1.10.1
Released February 23, 2021.
New And Noteworthy
- This release of the Microsoft Common Data Service (CDS) Connector was built against version 9.0.45.3930 of the Microsoft Dynamics 365 SDK.
- Added support for Client Secret authentication. (SCMSCDS-108)
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-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)
SCMSCDS-162
The Connector was unable to access custom N:N related entities.
SCMSCDS-163
Enabling Batch Processing on Upsert operations caused Statecode and Statuscodes to be set to default values for inserted records.
Known Issues
SCMSCRM-381
Summary: When modifying Connections that use the Azure AD deployment type, the Connection dialog displays the default URL, but does not save it causing the Connection to fail.
Workaround: Edit the URL in some way, such as adding an ending backslash or retyping part of the URL.
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.
SCMSCDS-208
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 SCMSCDS-205.
SCMSCDS-206
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 SCMSCDS-204.
SCMSCDS-197
Summary: The connector is not parsing the targeted organization URL properly to get the organization name, which prevents a connection to the service and generates errors similar to the following: (Case # 01898475, 01912925, 01916422, 01922701, 01923813, 01929948, 01931170, 01934189, 01941890, 01949528, 02040746)
"Message : Verify that the Organization is correct and that you can connect to the same Organization from the system running the Scribe Online Agent.
The following exception message was returned:
Length cannot be less than zero.
Parameter name: length."
Workaround: Contact Support for hotfix SCMSCDS-198.
SCMSCDS-190
Summary: When configuring a Connection with Client Secret authentication using the TIBCO Scribe® Online API, the deployment type in the model is set using "ClientSecret". If you later open the Connection dialog in the User Interface for the Connection created via the API, the Deployment Type field displays as Online and must be corrected. If you never open the Connection configuration in the User Interface, the Connection remains configured correctly and can be used without issue.
Workaround: Use the number "4" in the model to set the deployment type as ClientSecret or open the Connection in the User Interface and set the Deployment Type to Client Secret.
SCMSCDS-186
Summary: When the skipseekunder field is mapped to false for Update, Create, or Upsert Blocks, unmapped fields are not available in operation results for subsequent operations.
Workaround: Map any fields you need in subsequent operations.
68058
Summary: The UserSettings entity is not available in the metadata for the Microsoft Common Data Service (CDS) Connector.
Workaround: None.
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.
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:
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.
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.
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:
The 'RetrieveMultiple' method does not support entities of type 'systemusermanagermap'.
Workaround: Use a Replication Solution instead.
Version 1.8.1
Released October 4, 2109.
New And Noteworthy
- This release of the Microsoft Common Data Service (CDS) Connector was built against version 9.0.2.12 of the Microsoft Dynamics 365 SDK. (SCMSCRM-212)
- Added support for multi-factor authentication when using Azure AD to authenticate. Existing Azure AD Connections will continue to work using the prior authentication method until you modify the Connection and reauthenticate. (SCMSCRM-236)
- Enhanced exception handling to detect, wait, and retry if the Microsoft Dynamics 365 / CRM API limits are exceeded. (SCMSCRM-120)
- Provided support for Alternate Keys for additional entities that support Upsert, including invoicedetail, quotedetail, and salesorderdetail. (SCMSCRM-231)
Migration And Compatibility
Replication Solutions Net Change Filters
64825 / 72377 / SCMSCRM-61
When a group of changes was written to Microsoft Common Data Service (CDS) all at the same time, only a portion of them were returned by a subsequent query because the Microsoft Common Data Service (CDS) 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.
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 Common Data Service (CDS) 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 Common Data Service (CDS) 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:
- Reset metadata for your Microsoft Common Data Service (CDS) Connections.
- Open any Replication Solutions that use Microsoft Common Data Service (CDS) as a source and replicate Recommended Entities.
- Change the Entities selection on the Solution to either All entities or Selected entities.
- Allow the Solution to save and finish preparing.
- 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:
- Existing Replication Solutions will continue to run with the original list of Recommended Entities unless you change from Recommended to Selected Entities or All Entities. If you go back to Recommended Entities, the new list is used.
- New Replication Solutions will use the new Recommended Entities. Any additional entities that are required can be configured in a second Replication Solution using the Selected Entities option.
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.
68432 / SCMSCRM-240
In some cases using FetchXML in the Native Query Block returned null values in fields for related entities.
69757 / 73952 / SCMSCRM-69
When connecting to Microsoft Common Data Service (CDS) V9.0 and, creating a Campaign Response only the Regarding and Owner Activity Party records were created, but not the Customer Activity Party record.
73236 / 73458 / SCMSCRM-65
For the Opportunity entity, the Microsoft Common Data Service (CDS) 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:
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'
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.
Note: See the Changes To TIBCO Scribe® Online Connector for Microsoft Dynamics 365 / CRM Replication Solutions Knowledge Base article for detailed information on this change.
66478 / 67597 / 69918 / SCMSCRM-39
Unable to process query results when an unsolicited relationship was returned in the query request.
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.
75508 / 75655 / SCMSCRM-11
When the virtual entity msdyn_componentlayer was present in a Microsoft Common Data Service (CDS) Organization, selecting the Recommended Entities option for a Replication Solution generated errors similar to the following: Error in call to child Process
SCMSCRM-8
The Microsoft Common Data Service (CDS) Connector generated paging cookie errors on the msdyn_solutioncomponentsummary entity when replicating all entities.
SCMSCRM-5
Excluded the rollupjob entity from the list of entities that can be replicated.
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 February 19, 2019.
New And Noteworthy
- This release of the Microsoft Common Data Service (CDS) Connector was built against version 9.0.2.4 of the Microsoft Dynamics 365 SDK.
- Supports all entities in the database that support Query, Create, Update, or Delete operations.
- Supports the FetchXML query language in a Native Query Block.
Closed Issues
There are no Closed Issues in this release.
