Leveraging a custom trigger to delete a Lead from a customer journey doesnt work

(1) Share

Report

Posted on by Wiz of D365M

It would seem that if you create a custom trigger

.. and try to use it in the end of a customer journey, using the /Activate a custom trigger/

.. you can only map the attributes to the /Lead ID/

.. the problem is the Lead Id IS NOT stored in the /Lead ID/ column of the Lead table, ...

... its stored in the /Lead/ column of the /Lead/ table

Since you can't map to the /Lead/ column in the /Activate custom trigger/ tile, is would seem impossible to hand over the lead id to a power automate flow (in order to update or delete the lead)

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Suggested answer

Haig Liu Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi,

Unfortunately, the Lead (leadid) field is a GUID field and cannot interact with other components or fields.

So I used the XRMToolbox tool to update the /Lead ID/ field with the /lead/ field value.

update lead set msdyncrm_leadid = leadid; select leadid,msdyncrm_leadid from lead;

1. Install XRMToolbox
2.Search the Tool Library to install SQL 4 CDS
3.Connect XRMToolbox to your environment.
4.Use the update code code and execute

I hope this helps, but please let me know if you need anything else or if you have any other questions.
thanks,
Haig Liu

Was this reply helpful? Yes No
Suggested answer

Josh O'Dea 8 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I have documented the solution here: https://jmdaily.com/customer-insights-formally-dynamics-365-marketing-leverage-journeys-and-power-automate-flow-for-lead-and-contact-record-updates/

Hope this helps!

Kind regards,

Josh

Was this reply helpful? Yes No
Wiz of D365M 28 on at

Like (0)

Report
Copy link

Link copied!

@Josh O'Dea - thanks. As far as I can see in my environments the Profile ID attribute of the Lead entity is equally empty for leads created by form submission. I would think that is the case for environments w/o "Customer Insights - Data".

@Haig Lui - seems the thing to do. But the strange thing is, the Lead attribute works just fine in fresh trials. I have a hunch something breaks if I do a Publish All Customizations, which is a bit frightening

Was this reply helpful? Yes No
Haig Liu Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@Wiz of D365M - Actually, what I do is not complicated. Just used the tool to copy and paste the /lead/ field value into the /lead ID/ field, and the changes have been fed into the dataverse and everything is working fine.
But here's the problem: it's not an automated process, I have to manually copy-paste the completion each time. And if at some point in the future we need to use the /lead ID/ field, we'll find that its value is already taken by /lead/.

Inability to use /lead/ field values directly makes for a dilemma.

Was this reply helpful? Yes No
Josh O'Dea 8 on at

Like (1)

Report
Copy link

Link copied!

Hi @Wiz of D365M

The profile id is available OOB with Customer Insights Journeys. Could you please try creating a new trigger without any additional fields. I believe the "Lead Identifier" field may actually be causing the problem here. Creating a new trigger with no additional fields should do the trick.

Let me know how you go.

Kind regards,

Josh

Was this reply helpful? Yes No
Verified answer

Wiz of D365M 28 on at

Like (0)

Report
Copy link

Link copied!

The Profile ID hinted by Josh is NOT the Profile ID in the Lead table (msdyncrm_profileid) , but a "mysterious" msdynmkt_profileid

Was this reply helpful? Yes No