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) / Business Process Error...
Microsoft Dynamics CRM (Archived)

Business Process Error - Cannot find record to be updated

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

I have a real-time workflow activated to update the Account field in an Opportunity when the originating Lead is qualified. This is because OOB CRM 2013 maps the Full Name of the Lead (as a Contact) to the customerid field in the Opportunity. My workflow works when run as System Administrator, but as any other user it fails with the error: "Sync workflow failed with error message - Unhandled Exception: Microsoft.Crm.CrmException: Cannot find record to be updated." The security role has full access to both the Lead and Opportunity so something else is preventing them from executing the workflow.

The logic of the workflow is as follows:

Workflow type: Real-time

Run on entity: Lead

Start when: Status Changes

Actions: Update: Qualifying Opportunity

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at

    It is obviously running too soon, when the Lead is Qualified but the Opp has not been created yet. Running it as a background workflow might work, but will probably still break occasionally.

    You could run it as a background workflow and add a short wait (1 minute?)

    Best bet though, would be to run the workflow on create of the Opportunity, check if it has an originating lead, and the customer is a contact, then update it to the parent account of the contact (check that it has one)

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

    Thanks Adam, I should've mentioned that I did try your second suggestion with the same result.

    I guess the curious thing to me is why it should run ok as System Admin, but not as another user. This would seem to imply that it isn't a timing issue.

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

    When I convert it to a background process, it does nothing. When I qualify the Lead, the workflow doesn't fire at all.

  • purwar purwar Profile Picture
    purwar purwar 2,836 on at

    Kindly check scope of workflow: it should be organizational , Kindly check it.

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

    Yes, it is set to Organization

  • Community Member Profile Picture
    Community Member on at

    Hi Joerbs,

    Could you try to set Administration role to another user and retry?

    Thanks

  • Suggested answer
    barry.carter Profile Picture
    barry.carter 85 on at

    Hi Joe,

    I am using CRM 2013 SP1 and if you map the fields it should populate automatically.

    Lead to Opportunity mapping:

    Parent Account for Lead (parentaccountid) to Account (parentaccountid)

    Parrent Contact for Lead (parentcontactid) to Contact (parentcontactid)

    Hope this helps

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