Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

  • 1.  stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    SILVER CONTRIBUTOR
    Posted Feb 07, 2019 02:39 PM
    Recently, we ran into an issue with a client's go-live where a deprecated feature (https://docs.microsoft.com/en-us/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#legacy-process-related-attributes-in-entities-are-deprecated) was removed from the D365 Production org via the deployment of a patch. This caught us by surprise because we did not experience the issue in the Dev or Test orgs and it was not removed as part of a major release as mentioned in Microsoft's documentation (see link above):

    "Deprecated" means we intend to remove the feature or capability from a future major release of Dynamics 365. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few years. After removal, the feature or capability will no longer work. We are notifying you now so you have sufficient time to plan and update your code before the feature or capability is removed.

    Here are more details on the issue:

    SYMPTOM
    When using Business Process Flow on opportunity, the stepname field (native display name is 'Pipeline Phase') is no longer being populated. This field is typically used in views, charts, reports, and Power BI to show what stage of the BPF is active. Since the field is no longer being populated, any solution components that reference it will no longer work.

    WORK AROUND
    To address this, we added a workflow on the Opportunity Sales Process entity that triggers when the opportunity sales process is activated, or changes stage, and sets both the stepname and a new custom field on the opportunity. We added the new field because, in addition to no longer populating the stepname, Microsoft might one day remove it completely. The field could also be populated by a plugin, if desired. For new deployments, we would just use a custom field immediately and not use the native stepname field at all. Then any other solution components would reference the custom field from the beginning.

    #CustomerEngagement #Sales #Technical

    ​​​

    ------------------------------
    Michael Cross
    Senior Consultant
    eLogic
    Rochester NY
    ------------------------------
    Conference-CRMUG_200x200


  • 2.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    TOP CONTRIBUTOR
    Posted Feb 08, 2019 06:53 AM
    We ran into this exact problem yesterday. While troubleshooting an unrelated issue, I noticed that the stage of our opportunities wasn't being updated as expected as you moved from one step to another. So other automation that also rely on the stepname were also not working (but not throwing errors).

    I came to the same conclusion as you (minus the new field component). I have the process populate that field on activation or step change. I've noticed this doesn't cover every case exactly as I'd hoped, but by our typical convention, it should work. I think I may go back and create a new field like you, because you bring up a good point that the internal field could go away in a future update.

    For your information, here's where this doesn't work:

    1. You apply BPF A and it sets the opportunity stepname to "Step 1"
    2. You advance BPF A to the next step, so the opportunity stepname is updated to "Step 2"
    3. You apply a new process (BPF B) that also populates the stepname. Because it's a new instance, stepname is updated to "Step 1"
    4. You re-apply BPF A
    5. Opportunity stepname is still "Step 1", even though the active step of BPF A is "Step 2"

    ------------------------------
    Steve Platz
    Technical Lead, Commercial Excellence
    LORD Corporation
    Cary NC
    ------------------------------

    Conference-CRMUG_200x200


  • 3.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    GOLD CONTRIBUTOR
    Posted Feb 08, 2019 09:41 AM
    Thanks for posting this as we've been running into the same issue and have had had problems with the Stages in the bpf for a while.  We've thought about adding a new field but didn't want to duplicate data but it sounds like this might be the best solution.

    Does anyone know how Microsoft is planning for users to consume the data in the future?  The default Pipeline chart still uses the Pipeline Phase field, I would hope that they have some direction or solution to view the phase of a bpf in the future.

    ------------------------------
    Eric Veneziano
    Sales System Analyst
    Minitab, Inc.
    State College PA
    ------------------------------

    Conference-CRMUG_200x200


  • 4.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    TOP CONTRIBUTOR
    Posted Feb 11, 2019 05:42 AM
    Hi all,
    We had the same issue and I raised a MS Support Ticket a couple of weeks ago.  They have reverted the deprecation of the stepname field.  I've created an opportunity today and stepname is now being populated.  We are on version 1710 (9.1.0.2048) online.  Please check whether this change has been applied to your environments.
    Regards,

    ------------------------------
    Mark Aston
    Data Analyst
    Ordnance Survey
    Southampton, UK
    ------------------------------

    Conference-CRMUG_200x200


  • 5.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    Posted Feb 11, 2019 12:11 PM
    @Mark Aston, that's great news! We are still on an earlier version 9.1.0.1856 but it is back to working for us too!

    My concern is that Microsoft will still depreciate it soon so we do need to find a solution while we have time.
    We've tried the suggested above approach but the Workflow only puts in the name of the Stage into the Pipeline Phase field while the original process inserts 'stepnumber'-'stepname', for example 2-Develop. So all the views using the Pipeline Phase in filtering still won't work properly.

    Another issue I found with this workaround is that it only works with opportunities that have a corresponding record in the Opportunity Sales Process entity but I already found at least one opportunity missing from there.

    Am I missing something because I saw a few articles talking how the Opportunity Sales Process workflow fixes the depreciated process but it doesn't work for us?


    ------------------------------
    Maryna Wandschneider
    MacDonald-Miller Facility Solutions, Inc.
    Seattle WA
    ------------------------------

    Conference-CRMUG_200x200


  • 6.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    TOP CONTRIBUTOR
    Posted Feb 12, 2019 05:03 AM
    Mark,
    That's good news that MS has backed off of pipeline phase, but we all know MS is going to get what MS wants, and to Eric's point, what replaces it?

    Is there any information or recommendations released from MS on how we should replace our dependency on the pipeline phase and still retain the ability to provide a 3-4 stage grouping in the pipeline phase graph for sales management, yet allow up to 10 process flows to have 5, 6, 7, or more stages to support front line sales' life cycles?

    Thanks,

    ------------------------------
    Jim Corriveau
    A.W. Chesterton Company
    Groveland MA
    ------------------------------

    Conference-CRMUG_200x200


  • 7.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    Posted Feb 13, 2019 08:53 AM
    I have seen the same behavior with numerous clients of ours. The approach we took was creating a workflow to update this field. I had to also update the existing Opportunity by running the newly created workflow.

    ------------------------------
    Ankit M Patel
    Dynamics 365 Consultant
    SA Global
    ------------------------------

    Conference-CRMUG_200x200


  • 8.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    Posted Feb 14, 2019 09:57 AM
    We ran into the same issue...Microsoft appeared to have broken something in the back end. We initially created a workflow to fix, but just as we decided to activate the workflow. Microsoft magically fixed the issue on their end.​

    ------------------------------
    Heath Purdy
    IT Operations Engineer
    ACIS
    Boston MA
    ------------------------------

    Conference-CRMUG_200x200


  • 9.  RE: stepname (Pipeline Phase) field on Opportunity no longer being updated when BPF stage changes

    TOP CONTRIBUTOR
    Posted 8 days ago
    Don't Panic! :)  It has been 10 months since this issue first hit a few random customers and was fixed fairly quickly. The MS documentation says they will deprecate StageID, but none of my customers have reported issues with the Pipeline Phase. There is no credible evidence that Pipeline Phase will go away any time soon.

    ------------------------------
    If this answered your question, please click on the arrow button next to Reply Inline and choose 'Make Best Answer.'
    Thanks.
    Nelson Johnson, Solution Architect
    BroadPoint, Inc., Bethesda MD
    Link with me! https://www.linkedin.com/in/nelsonjohnson/
    ------------------------------

    Conference-CRMUG_200x200


If you've found this thread useful, dive deeper into User Group community content by role