0
Answered
Aneesh Varghese 2 months ago in Identity Broker for Microsoft Dynamics CRM • updated 2 months ago 4

Previous Version: Microsoft Dynamics CRM Connector v4.1.1.1

Upgraded Version: Microsoft Dynamics CRM Connector v5.1.0.1

Observing a strange behaviour after the Connector upgrade. Exports are successful from IdB and FIM point of view but the changes are not reflected in CRM.

The above mentioned behaviour is happening only for new users/records or if the attribute is "Null" or blank in CRM. Changes are appearing correctly if the attribute is already populated with something (existing contact/record).

Please advise what details you need to troubleshoot this issue.

I already performed the following:

  • Checked the IdB logs but couldn't find any errors
  • Checked with the CRM team
  • Captured the TCP traffic but found the SOAP message is pretty much encrypted
Affected Versions:
Fixed by Version:

Answer

Answer
Answered

Hi Aneesh,

Here is a patch that should hopefully resolve this issue. Could you backup (to a different location) and replace the Unify.IdentityBroker.Communicator.DynamicsCRM.dll that is currently in the Identity Broker/Services directory with the patched version below.

Unify.IdentityBroker.Communicator.DynamicsCRM.dll

GOOD, I'M SATISFIED
Satisfaction mark by Aneesh Varghese 2 months ago
Answer
Answered

Hi Aneesh,

Here is a patch that should hopefully resolve this issue. Could you backup (to a different location) and replace the Unify.IdentityBroker.Communicator.DynamicsCRM.dll that is currently in the Identity Broker/Services directory with the patched version below.

Unify.IdentityBroker.Communicator.DynamicsCRM.dll

Thanks Beau! I applied the patch in the Test environment. I will let you know if any other issues.

+1

I've experienced the same issue. Confirming the patch/fix has worked for me to correct the issue :)

I can also confirm that the patch has resolved the issue.