Hi,
i got a requirement where client want to develop 2 scenarios:
1. Ability to add one lead to many opportunities
2. Ability to add multiple leads to one opportunity.
To fulfill above scenario, I have created 1:N relationship for both Lead-Opportunity and Opportunity-Lead. Now user is able to add multiple opportunities in lead but not able to see the same lead in the Lead-subgrid present on opportunity page.
when user explicitly tried to add the same lead to respective opportunity, it throws an 'already associated' error.
Please tell me the solution on how we can achieve this scenario.
*This post is locked for comments
You will get this error if you will try to associate, already associated entity and you can only do this if you have n:n relationship. so for n:n
thanks
Hi,
To acheive your requirement you need to create N:N relationship between lead & opportunity. If the native N:N doesn't work in your case hen you can try manuall N;N i.e. create a custom entity say 'Lead Mapping' with a lookup to lead & opportunity. Then add subgrid to lead & opportunity entoity for this entity.
So now, on lead & opportunity, you can have multiple opportunities or leads.
You can do reporting on this entity as well.
Hope this helps.
Thanks Mahen for the reply.
i have implemented both the relationships in lead and opportunity page but when i add existing opportunity in opportunity-subgrid on Lead entity, then the same lead should be visible in the lead-subgird of this opportunity. After implementing these relationships, lead is not populating in the lead-subgrid of opportunity page and when i add it explicitly it shows 'already attached' error.
Thanks Iswarya for the response.
If i use N:N relationship then it will loses the reporting ability and tracking ability of the leads and opportunity.
Can we have any other approach?
Hi,
When you setup 1:N relationship in child entity you will get lookup of parent entity and in the parent entity you can have subgrid where you can see all the associated child records. So as you have created 1:N relationship and you are able to add subgrid of opportunity into parent (lead) entity, so if you want the same behaviour in opportunity, you have to create 1:n between opportunity to lead.
Thanks
hi vinit,
you should use N:N relationship to achieve this functionality
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156