'Sitecore.DataExchange.Tools.DynamicsConnect.Models.DynamicsConnectCollectionModel, 1.0' does not have a remote version

I was using Sitecore Connect™ for Microsoft Dynamics 365 for Sales 7.0.0 in Sitecore 10.2. To use this module, I have installed Sitecore Connect™ for Microsoft Dynamics 365 for Sales 7.0.0 and Data Exchange Framework 7.0.0 as it was mentioned here.

For the end points , in this location /sitecore/system/Data Exchange/Connect for Dynamics Tenant Branch/Endpoints/Providers/xConnect/xConnect Client Endpoint, I have added Collection Service Connection String Name (xconnect.collection) and Collection Service Certificate Connection String Name (xconnect.collection.certificate).

To test the connection, I clicked on the “Run Troubleshoot” button

After that below exception was coming.

Solution:

To solve this issue, I performed the below steps:

Go to this location /sitecore/system/Data Exchange/Connect for Dynamics Tenant Branch/Endpoints/Providers/xConnect/xConnect Client Endpoint.
Go to the Collection Model Path which is /sitecore/system/Settings/Data Exchange/Providers/xConnect/Collection Models/Connect for Dynamics/Connect for Dynamics Collection Model.
Click on Convert Model to JSON, and it will download the JSON file.

Deploy this JSON file to below two locations:

<xConnectWebsite>\App_Data\jobs\continuous\IndexWorker\App_Data\Models
<xConnectWebsite>\App_Data\Models

Comments

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine’” on Windows 11

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine' ” on Windows 11 Today I started to install Sitecore 10.2 using Sitecore Instance Manager on Windows 11 and I got this issue “Failed to start service ‘Sitecore Marketing Automation Engine' ” . Error : On event viewer it was showing the below error: I also tried to run ‘ Sitecore.MAEngine.exe ’ like this C:\Windows\system32>C:\inetpub\wwwroot\sclocal102xconnect.dev.local\App_Data\jobs\continuous\AutomationEngine\Sitecore.MAEngine.exe Which was throwing below error: Starting Marketing Automation Engine... 2022-01-29 22:21:11 ERR Error initializing XConnect client. System.AggregateException: One or more errors occurred. ---> Sitecore.XConnect.XdbCollectionUnavailableException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected err

Azure AD Integration with Sitecore 10.2

Azure AD Integration with Sitecore 10.2 Sitecore identity server that comes with Sitecore 9.1 allows you to log in through an external identity provider like Azure Active Directory, Facebook, Apple, or Google. It is built on Federation Authentication. What is Federation Authentication? Federation authentication is a technology to allows users to access multiples application, tools, and domains using one credential. Using one set of credential user can access multiple applications, and resources after authentication. Federation authentication consists of two systems, the Identity provider and the Service provider. Identity providers that maintain/create/manage identity information like name, email address, device, and location. Some examples of identity providers are Azure AD, Google, Facebook, and Apple. Service providers basically refer to a website, software, or app that the user is trying to access and SP basically relies on the identity provider to authenticate the user and provi

Sitecore Custom API Issue with Federation Authentication

Sitecore Custom API Issue with Federation Authentication In earlier segments, detailed in Part 1 and Part 2 of the blogs on Keycloak Integration with Sitecore, I introduced Keycloak functionality for CM login. Concurrently, I addressed a necessity to develop custom APIs for retrieving Sitecore users and roles. Following the development of custom APIs, during authentication failures, the API erroneously returned a status code of 200 instead of 401. The problem arose because API requests were being routed through the "owin.identityProviders" pipeline, which was not intended for API usage. Solution: When OWIN identifies a 401 response and the AuthenticationMode is set to "Active," it fails to capture the URL hash included in the request. Another choice is to activate the "Passive" AuthenticationMode, wherein OWIN refrains from actively intercepting 401 responses. In passive mode, your application needs to explicitly issue a Challenge to trigger the OWIN aut

Swati Gupta (3x Sitecore MVP) | Blogs

Search This Blog