Announcements
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
It doesn't appear I can run any synchronous workflows as any user other than System Administrator. When I try to run the real-time workflow from the Opportunity I get a different Business Process error message with NO details, only that 'Sync workflow terminates with error ''.
The user is the Owner of both the Lead and the resulting Opportunity.
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
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.
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.
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?
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.
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
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)
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.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
54
#3
dkrishna
6
Share
Report
All responses (
Answers (
