Dynamics Community Forum Thread Details

Odd behavior when two Contacts are merged - workflows initiated by related Contact lookup field change

Let's have

Contact A and Contact B, which are considered duplicates
Record C in table ExampleEntity
- N:1 relationship between Contact and ExampleEntity: lookup field for Contact
- field/column Email
Contact B is in Record C's Contact lookup field
There's a real-time ExampleEntity Workflow which initiates at Contact lookup field change: it stores Contact emailaddress1 to Record C's field Email.

Let Contact A emailaddress1 be email@domain.com

Let Contact B emailaddress1 be newemali@domain.com

As Contact A and Contact B are considered duplicates, we merge them with the built-in Merge functionality. We choose Contact A as the primary Contact and to keep Contact B's emailaddress1

During merge, it seems, that

first all relationships are written from Contact B to Contact A
this causes Contact B be replaced by Contact A in Record C's lookup field
Workflow starts and records Contact A's emailaddress1 to Record C's Email
only now the merge updates Contact B emailaddress1 to Contact A. The Workflow has already done the damage, replacing the new email with old email.

It's kind of ok that the merge initiates the Workflow but it is very sad that it runs too early.

Any thoughts?

Best,

Jani

Quick Links

Leaderboard