Skip to main content

Notifications

Microsoft Dynamics CRM (Archived)

Can't change stage of BPF on old opportunities

Posted on by 70

Hi,

Could you please help me to solve this problem please ?
I can't change the stage on my business process flow for old opportunities 2018_2D00_02_2D00_09-15_5F00_51_5F00_39_2D00_Opportunity.png

I think that has happen since we migrated from CRM 2016 to Dynamics 365

Thank you

Camille

*This post is locked for comments

  • Thomas I Profile Picture
    Thomas I on at
    RE: Can't change stage of BPF on old opportunities

    I'm working with Camille, I did actually check the tables and noticed records are missing for opportunities created before migration ;)

    I guess there are no other way than to try an build a custom query to create the missing records, as I don't find any fix provided by microsoft...

  • gdas Profile Picture
    gdas 50,085 on at
    RE: Can't change stage of BPF on old opportunities

    Hi Camille,

    Seems this is migration issue .Check in the database and compare the table as Thomas suggested.

  • Thomas I Profile Picture
    Thomas I on at
    RE: Can't change stage of BPF on old opportunities

    Hi James and thanks for your help.

    I don't think the answer is what you suggest. I checked the database, and I notice that for the opportunities impacted there is a record in the "BusinessProcessFlowInstance" table but no record in the "OpportunitySalesProcess" table.

    All newly created opportunities have got a reference in both tables.

    My best guess, is that it is somehow a bug in the migration program, that did not properly update the existing opportunities.

    However, i did not find any confirmation nor solutions to that issue.....

    Rgds,

  • Suggested answer
    jestuder Profile Picture
    jestuder 156 on at
    RE: Can't change stage of BPF on old opportunities

    With your migration from 2016 to D365, Did you migrate any solutions from a sandbox instance to production?  It could be that the BPF is referencing a related record that has different GUID in each system.  Updating the BPF fixes the problem.  So I would first open the BPF in the editor and find any references where it is setting a value (in my example it was products) and if a specific record is referenced, navigate to it in the new system to set the proper GUID.  Then validate and save the BPF.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans