How to connect Business Central OnPrem to Common Data Service

(1) Share

Report

Posted on by Marco Mels

In Dynamics 365 Business Central v160 (16.5) we use OAUTH 2.0 as connection protocol instead of previous legacy protocols. After adding consent to the Azure AD app so that the solution can be injected to CDS, an error may be shown to the user and an event is written in the application event log file.

Application event log file:
Server instance: BC160
Category: Runtime
ClientSessionId: ed651d76-4dfc-41dc-804d-e96cff845704
ClientActivityId: 87f46331-46b0-4079-9c8b-10158b32d51c
ServerSessionUniqueId: 3cbfde90-7a7c-4e6a-8923-7c96b358f888
ServerActivityId: 9042176b-76ec-4ab3-961d-7f57318fa56a
EventTime: 09/25/2020 13:48:39
Message (NavNCLDialogException): This message had personal data removed. The original may still be in transient telemetry. Find it using the transientTelemetryId.
ParentException: NavNCLDialogException
Failed to acquire an access token for %1.

A workaround does exist. Download the following package from https://www.nuget.org/packages/Microsoft.Identity.Client/4.14.0. Extract the files and from \lib\net45, copy the following files to the Service folder of the NST (%programfiles%\Microsoft Dynamics 365 Business Central\160\Service).

Microsoft.Identity.Client.dll

Microsoft.Identity.Client.xml

NOTE: we expect version 14.0, a higher version will not work with 16.5.

Restart the NST. After that, that specific error will no longer occur and the CDS connection can be enabled or redeployed.

Thanks.

I have the same question (0)

All responses (5)

Answers (0)

Andy Sather on at

Like (0)

Report

Thanks Marco

Was this reply helpful? Yes No
Kazuma Nagayoshi on at

Like (0)

Report

Is this on-premises environment built with Docker? If you're in a Docker environment, you can ask them for help with an issue on GitHub.

github.com/.../navcontainerhelper

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

A new Common Data Service onboarding experience will be provided, where users will be able to connect to a Common Data Service environment and associate a Business Central company with a Common Data Service business unit. This will allow for multiple companies to connect to a Common Data Service environment. During setup, the Common Data Service connection entities from the default Common Data Service database will be synchronized.

Extensibility support for developers developing Business Central integrations for Common Data Service is provided. With the extensibility support, Business Central Extensions can be written to add fields and tables to the synchronization process, also extending existing tables. In addition, transformation can be created, transforming and mapping values.

Was this reply helpful? Yes No
BCCluj 5 on at

Like (1)

Report

Hi Marco,

Could it be that the same problem persist for BC17 Cu1 Om Prem?

After the admin consents, the page in BC stays open forever and nothing happens.

When closing it, the same message "Failed to acquire an access token for " appears.

Was this reply helpful? Yes No
Greg Enns 1,106 on at

Like (0)

Report

Marco Mels Are these the steps still applicable for BC20 on-prem to connect to CRM in the cloud?

I have Oauth working for my Production BC14 on-prem, but trying to get BC20 on-prem test environment connected to my cloud CRM sandbox environment and running into problems. Thanks in advance!

Was this reply helpful? Yes No