Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Some of my clients are reporting the following issue.
Basically, when they move on the Opportunity pipeline the field Pipeline Phase (stepname) use to be updated based on the step they currently are. However, the field is not being updated since this weekend.
Is anyone facing the same issue, the version number on these clients is 184.108.40.2068
Since you're talking about the Stage of the Business Process flow, this feature has been deprecated in D365 v9.
You can refer my blog for this and the workaround - d365demystified.com/.../bpf-process-stage-name-not-populating-on-records-in-d365-v9-deprecated-and-workaround
Hope this helps.
The deprecation anouncement mention only ProcessId, StageId, and TraversedPath not StepName. Do you know anywhere Microsoft mention anything about StepName (Pipeline Phase)?
I appear to be having the same issue.
Am now going to raise a ticket with MS.
DB version: 220.127.116.116
We raised a ticket with them and they confirmed the field is deprecated. They documented very poorly this time witch fields they are deprecating, it is really vague (https://docs.microsoft.com/en-us/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#legacy-process-related-attributes-in-entities-are-deprecated).
As you may know, the BPFs have their own entities now, so as a workaround, you can do this.
BTW, I would open the ticket with Microsoft, this way they can document it a better next time and avoid this kind of headaches.
Your article is about the StageID, not the Pipeline Phase. Yes, the StageID is deprecated, however I have not seen a problem with the Pipeline Phase, and it is not deprecated.
Business Applications communities