web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Qualify Lead is mappin...
Microsoft Dynamics CRM (Archived)

Qualify Lead is mapping Full Name to Potential Customer in CRM 2013

(0) ShareShare
ReportReport
Posted on by Joe Woltering 12,163

After I qualify a Lead, instead of mapping the Account from the 'Customer' field to Potential Customer in the resulting Opportunity (which is explicitly defined in the relationship mappings), it is taking the Full Name of the Lead, creating a Contact, and populating the Potential Customer field with the newly created Contact. What gives?

*This post is locked for comments

I have the same question (0)
  • ScottDurow Profile Picture
    ScottDurow 21 on at

    This is the the standard behaviour of CRM2013's lead qualification process. If you need to change this you can create a real time workflow to change the customer field to the account of the associated contact.

    Gus wrote about a similar issue here - www.zero2ten.com/.../processing-opportunities-created-after-qualifying-leads-on-the-new-user-experience-forms-in-microsoft-dynamics-crm

    Hope this helps,

    Scott

  • Joe Woltering Profile Picture
    Joe Woltering 12,163 on at

    Ugh. Yes, I have already put a workflow in place to do this. Thanks Scott.

    This is terrible, terrible logic on Microsoft's part. First off, we don't allow users to create Accounts, they are created by our ERP. Secondly, most of our Leads are from Customers who already have Accounts with us, so the requirement to maintain Account consistency from Lead to Opportunity seems like a no-brainer.

  • Joe Woltering Profile Picture
    Joe Woltering 12,163 on at

    OK, so now my workflow is failing, saying the it can't locate the record I am trying to update, which is the Qualifying Opportunity.

    Specifically,

    Plugin Trace:

    [Microsoft.Xrm.Sdk.Workflow: Microsoft.Xrm.Sdk.Workflow.Activities.UpdateEntity] [UpdateStep3]

     

    Error Message:

    Unhandled Exception: Microsoft.Crm.CrmException: Cannot find record to be updated    at Microsoft.Crm.Workflow.Services.UpdateActivityService.UpdateInternal(Entity entity, String stepId)    at Microsoft.Crm.Workflow.Services.UpdateActivityService.ExecuteInternal(ActivityContext executionContext, UpdateEntity updateEntity)    at Microsoft.Crm.Workflow.Services.UpdateActivityService.Execute(ActivityContext executionContext, UpdateEntity updateEntity)    at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)    at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

  • ScottDurow Profile Picture
    ScottDurow 21 on at

    Hi,

    This means that there isn't an opportunity related to the record- it could be that you are qualifying in bulk from the list view - the process seems to be different if you do it in bulk and not all record relationships are set.

    Hope this helps,

    Scott

  • Joe Woltering Profile Picture
    Joe Woltering 12,163 on at

    Hey Scott,

    It definitely exists. I click on 'Qualify' in the Lead and it opens up the new Opportuntiy, however the workflow doesn't fire and it claims that it doesn't exist, even though I am looking right at it. I am doing this for a single Lead.

  • ScottDurow Profile Picture
    ScottDurow 21 on at

    Hi,

    The qualify process doesn't update all the data at the same time - so make sure that your workflow is not firing too soon. What event & entity is your workflow firing on?

  • Joe Woltering Profile Picture
    Joe Woltering 12,163 on at

    Yeah, seems like a timing issue, but I thought that's why I should use a real-time workflow in this case. I have set it to fire when Lead status changes (assuming that once it's Qualified, it's status changes). It seemed to work the first couple of times I tested it, and now it doesn't work any longer. Then I tried from the reverse angle, by firing when the Opportunity is created and pull the Account info from the Originating Lead.

  • Joe Woltering Profile Picture
    Joe Woltering 12,163 on at

    So it seems like my problem is more related to who is qualifying the Lead/running the workflow. When I run it as myself (sysadmin) the real-time workflow fires as intended. However, if I qualify a lead as a generic salesperson, it fails with Business Process error that it 'Cannot find record to be updated'. I have specified in the workflow to run it as the owner of the workflow, which is myself aka System Administrator.

  • ScottDurow Profile Picture
    ScottDurow 21 on at

    Hi,

    It is most likely to be a permissions issue then where the sales person doesn't have access to the record that the workflow is trying to update. Check the role assigned to the sales person has access to all the records involved.

    Scott

  • Joe Woltering Profile Picture
    Joe Woltering 12,163 on at

    The user is the Owner of both the Lead and the resulting Opportunity.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans