Skip to content

x Want to ask a question or reply? Click here to join the group.
  • State Not Answered
  • Replies 2 replies
  • Subscribers 68 subscribers
  • Views 1641 views
  • Users 0 members are here
Browse Forums
Announcements
159
topics
32
replies
General Discussion
3k
topics
11k
replies
More Content

Adding Leads to Regarding field (comm_opportunityid) in Tasks

Simon Garthe
Posted By

Hello

When creating a task in the top screen "CommWebPicker" there is a field called "Regarding / comm_opportunityid".

With comm_opportunity id you can connect a task to the entities: OPPORTUNITY, CASE, ORDER and QUOTE.

I'm now trying to add entity LEAD to the advanced search field comm_opportunityid. 

To achieve this, I used Derived Fields Assistant and added cmli_comm_leadid and comm_leadid to entity communication. 

This enables me to choose Lead as a tied field

I can now choose Lead in Regarding field

-----

1. Task can be saved with lead assigned.

2. Reopening the task, the screen changes - looks fine for this step.

Problem:

3. Reopening the task again - but lead has already been converted to opportunity

If the Lead has already been converted to an opportunity, but the task is assigned to the LEAD then CRM automatically chooses a company (cmli_comm_companyid) and person (cmli_comm_personid).

Regaring field stays filled with Lead.

But when saving again:

Regarding field becomes empty and the task is not shown in the lead communications tab anymore. 

Only company and person are there.

How can I prevent this from happening?

I'm looking forward to any ideas and suggestions

Thanks

Simon

  • 0

    Hi Simon,

    I'm not sure why you needed to do any of that, as when you go to a Lead and create a communication it will link itself to the Lead. 

    When a lead is converted, the communications will follow it into the Opportunity. (Though if I go back and view the original Lead then I will only see the communications that existed whilst it was a Lead).

    The key thing to note here is that I went to the lead first, I didn't manually link the Communication to the Lead. 

  • 0 in reply to Matthew Shaw

    Hey Matthew,

    Thanks for your reply and input. This is a customer request to link tasks to leads. 

    Your approach is absouletly right and the way to go.

    Still, I can understand the customer request because why would you be able to create a task and link it to an opportunity, order and so on from everywhere without having to go the the entity first but not for lead? 

    Have a nice day!

*Community Hub is the new name for Sage City