This hotfix can be downloaded from the
TIBCO Support Portal. You must be logged in to the Support Portal to enable the hotfix downloads. After logging in to the portal, select the
Downloads menu option and select
Hotfixes from the dropdown menu. Then navigate to
AvailableDownloads/Scribe/Insight/Adapters/CRM/5.6.2/hotfix-14. See the attached readme file for installation and uninstallation instructions.
Insight 7.9.5 must be installed on the server prior to installing this hotfix. Insight 7.9.5 is available for download on
TIBCO eDelivery for customers that have an active maintenance agreement. To inquire about renewing maintenance, contact the TIBCO Renewals team.
The main reason for this hotfix is compatibility with different authentication types offered by Microsoft for the Dynamics CRM / CE products. The hotfix adds support for Azure AD authentication and restores compatibility with Partner Hosted (IFD) authentication, which was not supported by Hotfix 11. The hotfix adds the Connection String option for authentication as a replacement for Partner Hosted (IFD) authentication, which will be affected when Microsoft deprecates WS-Trust.
If you are using the "Online" deployment type with the Adapter, you must use Azure AD authentication instead because Microsoft will eventually turn off the Regional Discovery Service. It is best to make this change when you can plan time for it and avoid any chance of disruption to your integrations. See this
Microsoft documentation for more information about when the changes the regional Discovery Service and to WS-Trust will affect your Microsoft CRM organization.
Requirements for using Azure AD:
- Use the hotfix installer to install the TIBCO Scribe Adapter For Microsoft Dynamics 365 And CRM.
- Set up an Azure AD Application for your organization in Microsoft Dynamics 365 / CRM with API permissions for Microsoft Dynamics 365 / CRM and a secret created specifically for this application.
- Create an application user in Microsoft Dynamics 365 / CRM for Customer Engagement that references the application ID of the Azure AD application and has System Administrator and System Customizer roles.
- In TIBCO Scribe Insight, when configuring your Microsoft Dynamics 365 / CRM connection, choose the Azure AD - Client Credentials authorization type. Enter the Client ID and Client Secret associated with the Azure AD application you created.
- The default URL will be the discovery service URL. You must change this to your organization's instance URL in this format: https://<yourcompany>.crm.dynamics.com.
- Verify your connection works and test your DTS files.
If you are using the Partner Hosted (IFD) deployment type, we encourage you to transition to using the Connection String before Microsoft deprecates WS-Trust.
You can read more about how to connect using Azure AD and the Connection String in the
Adapter help.
================================================================================
Closed Issues in 5.6.2_HF-14 (This Release)
This hotfix replaces HF-11.
SCINSIGHT-210
This hotfix adds support for Azure AD authentication and restores compatibility
with IFD authentication. If you are using the "Online" deployment type with the
Adapter, we encourage you to use Azure AD authentication instead because
Microsoft will eventually discontinue the regional Discovery Service which is
used by the Adapter. It is best to make this change when you can plan time for
it and avoid any chance of disruption to your integrations.
See this article for more information:
https://support.tibco.com/s/article/TIBCO-Scribe-Insight-Adapter-for-Microsoft-Dynamics-365-And-CRM-5-6-2-hotfix-14
See this help topic for information about connecting using the Adapter:
https://help.scribesoft.com/scribeinsight/en/index.htm#Subsystems/AdapterForDynamicsCRM/implementingtheadapter/connecting_to_the_adapter.htm
SCINSIGHT-201
Added the ability to use a Connection String to connect to CRM.
Microsoft will eventually deprecate the WS-Trust authentication type. This means
that the Partner-Hosted (IFD) deployment option in the Adapter will stop working
at some point in the future. Best practice is to transition your IFD based
connections to the Connection String type before Microsoft deprecates WS-Trust.
See this Microsoft documentation for more information about when these changes
will affect your Microsoft CRM organization.
https://docs.microsoft.com/en-us/power-platform/important-changes-coming#deprecation-of-office365-authentication-type-and-organizationserviceproxy-class-for-connecting-to-dataverse
To use Dynamics 365 in a Connection String deployment with IFD, you
must create a Dynamics 365 user as the integration user. This must be a different
user than the default INTEGRATION user. For IFD, Dynamics 365 does not have
access to the Active Directory information required to use the default
INTEGRATION User.
See the Adapter help for more information about how to connect using the
Connection String.
================================================================================
Closed Issues in 5.6.2_HF-11
SCINSIGHT-111
Resolved issue of deprecation of the regional Discovery Service & WS-Trust in
new CRM instances/new users. This release will require you setup Azure AD client
credentials in CRM to authenticate using Client ID and Client Secret.
================================================================================
Closed Issues in 5.6.2_HF-07
SCINSIGHT-127
Added additional retry logic when the Microsoft Discovery Service does not
respond in a timely fashion and addressed an issue with upserts that could
occur if customer is on latest Microsoft Dynamics CRM patch.
SCINSIGHT-132
Resolved the issue where sorting parent objects and child objects in a custom
query could cause records to be missing from the query results.
================================================================================
Closed Issues in 5.6.2_HF-06
SCINSIGHT-86
Resolved the issues with the CRM Adapter not producing an error when the batch
size is smaller than the number of child entities being returned.
================================================================================
Closed Issues in 5.6.2_HF-05
SCINSIGHT-94
Resolved the issues with the CRM Adapter not recovering after hitting Microsoft
API Limit in CRM.
================================================================================
Closed Issues in 5.6.2_HF-04
SCINSIGHT-75
Resolved the issues loading metadata when some default tables and relationships
were missing in CRM.
================================================================================
Closed Issues in 5.6.2_HF-03
SCINSIGHT-45
Addressed slow performance in CRM when the Publisher is active and objects are
selected for publishing.
================================================================================
Closed Issues in 5.6.2_HF-02
SCINSIGHT-30
Fixed the Out of Memory Exception error or Object reference error that occurred
when refreshing adapter metadata.
================================================================================