Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
Hi this is just a general discussion,
On updating the status reason based on moving through a business process flow
There are ways to update status reason by workflow on stage exit and you can use JS etc...
Previously this could be done out of the box straight forward but -As step-name has been deprecated https://www.crmug.com/communities/community-home/digestviewer/viewthread?MessageKey=e1bbd066-ef76-40cc-bb8b-402dbb8dd647&CommunityKey=dc83c23b-ede0-4070-ae7a-dd90859148a6&tab=digestviewer
Just wondering what everyone else is doing within the wider community when it comes to updating status reasons
You could/should create a workflow for the BPF entity with trigger on change of Active Stage to set the Status Reason of the related entity record.
I hope you are well!
Many thanks for the reply I have done similar to this and also using the generic Stage exit/entry on BPF - are there any plans you are aware of for Microsoft to set this Out of the box?
You can even use Business Rules to set the pipeline phase or status reason on the related record, but the form should be saved to commit the change.
See example: crmkeeper.com/.../
Since there can be multiple instances of multiple BPF's active on one record, I don't think an Out of the box solution can be expected.
Very good point but we historically were able to do this using the stepname- for certain projects I have seen It's been re-created using a realtime workflow and a text field to write the values in. Really good/useful ideas to consider though many thanks as usual Stefan!
Business Applications communities