Dynamics Connector Integration Key Error after updating to Connector V2 RU1

(0) Share

Report

Posted on by Shaun S

Hi,

I have updated to the connector version 2 RU1 and have found that the account to customer service map fails with the below error:

[Account to Customer Service] has encountered an error while processing key [[Koorb Test 2, c9897645-ded6-e111-9b6d-d8d3855b354e]]. The territory with id c337ef7b-6ad4-e111-9b6d-d8d3855b354e was not found to have a value for it's dynamics_integrationkey attribute when looking up the territoryid property.

It appears that whenever a lookup field is set on the account, the connector attempts to find the integration key value and fails as not all entities are configured to be integrated. For example the territory entity.

For the mean time as a workaround I will configure the territory entity for integration.

Has anyone else encountered this problem?

Thanks Shaun

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (2)

Sort by

Verified answer

Konstantin Levchenko 1,410 on at

Like (0)

Report
Copy link

Link copied!

Hi Shaun,

You did everything correctly.

If you want to use in your mapping any Lookup Field for Entity not included in integration process, then you should:

1. Add this entity in integration (this will allow Connector to create Dynamics Integration Key field in this Entity)

2. Do Initial synchronization for added entity (this will allow to populate values in Dynamics Integration Key)

After those steps you should be able to use in your maps lookup filed for this Entity. This is the normal behaviour for Connector.

Cheers,

Konstantin

Was this reply helpful? Yes No
Shaun S on at

Like (0)

Report
Copy link

Link copied!

Hi Konstantin,

Thanks for the reply. The problem I have is that I am not mapping the territory field in the account to customer service map. But the connector checks the entity for the integration key field regardless of whether its being mapped or not.

I would expect this error should only be thrown if the lookup field is actually mapped. Otherwise we need to setup additional entities for integration that we don't intend to integrate.

Cheers,

Shaun

Was this reply helpful? Yes No
Verified answer

Surmeet Singh 3,075 on at

Like (0)

Report
Copy link

Link copied!

Hi Shaun,

This problem Seems to be similar to selecting a primary contact on the customer which gives error when selected on Account Form in CRM even though it is not mapped.

You can change the Account object provider by commenting the territoryid, this should work.

Was this reply helpful? Yes No
Derek Nachimow 70 on at

Like (0)

Report
Copy link

Link copied!

Shaun,

We you ever able to get this resolved? We're running into a similar issue.

Thanks.

Was this reply helpful? Yes No