Microsoft Dynamics 365 | Integration, Dataverse...

How can I map subgrid records from lead to opportunity?

(0) Share

Report

Posted on by Joseph Nasr

183

Hello,

I created a Many to Many Relationship between Leads and a custom table called 'Funding Entities'. In the Leads Form, I added a subgrid showing the related Funding Entities of that lead.

When I qualify that Lead to Opportunity, how can I map the records in that Lead's subgrid to the subgrid in the Opportunity Form?

If I go to the Lead's Field mappings to Opportunity, there is no field like 'Funding Entities'.

Any help will be highly appreciated.

Thank you in advance

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Leah Ju Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi Joseph Nasr,

Field mapping is only supported for 1:N relationships, and there is no OOB functionality for mapping N:N relationships at Qualifying Lead.

Before that, you will have to use plugins.

Now, you can use power automate to create one flow to achieve it.

Please refer to the following steps:

1.Make sure that there is also a N:N relationship between Opportunity and this custom table.

2.Power Automate

1)Trigger

--When you qualify one lead to opportunity, ‘Originating Lead’ field will be populated this lead automatically on opportunity.

--Using opportunity creation as trigger and this field as filter:

2)List rows--retrieve relationship entity.

-- The schema will look something like relationshipentitynameset

3)Get a row by ID

4)Relate rows:

https://learn.microsoft.com/en-us/power-automate/dataverse/relate-unrelate-rows

I hope you can mark my answer verified if it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah

Was this reply helpful? Yes No
Joseph Nasr 183 on at

Like (0)

Report
Copy link

Link copied!

Hello Leah,

How did you get the 'cr0e8_fundingentities_leadset' ?

Regards,

Was this reply helpful? Yes No
Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Joseph Nasr,

An N:N (many-to-many) relationship depends on a special relationship table (intersect table)

In power automate, the schema we need will look something like 'relationshiptableset'.

Here are the blog I referenced:

https://technologyblog.rsmus.com/technologies/microsoft/listing-records-related-through-an-nn-relationship-in-power-automate/

I hope you can mark my answer verified if it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah

Was this reply helpful? Yes No