Share
Report
4Hi everyone,
Need some guidance / help on this one...
If the Process Stage Name field in the Opportunity entity is no longer being updated (or no other field in the Opportunity entity represents the active stage), then the Active Stage name field from the Opportunity Sales Process entity needs to be available to be included in a view for the Opportunity entity.
I do understand that the Process Stage Name is deprecated; however, what field in the Opportunity entity replaces the representation of the Active Stage field? Is Pipeline Phase still available or deprecated too?
There is already a relationship between the Opportunity and Opportunity Sales Process entity. It is a 1:N relationship and therein lies the problem, because I can’t add the Active Stage field from the Opportunity Sales Process entity to a view for the Opportunity.
There is a big impact here as many clients would have the opportunity pipeline based off the value in either Process Stage Name or Pipeline Phase,
I can certainly create a workflow on the Opportunity Sales Process entity that, based on changes to the Active Stage value, updates a custom field on the Opportunity entity that represents the Active Stage. However, I shouldn’t have to write something like this for every client that is using Dynamics 365 for Sales and the Opportunity entity. Because after I put that workflow in place, then I must change every view, chart, form, workflow and custom code that references the Process Stage Name or Pipeline Phase fields.
This means that for every entity that has a Business Process Flow, a custom field and custom workflow has to be written in order for someone reviewing these records to have visibility to the Active Stage name. If that is the case, every customer that is on the 9.1 release and uses the Opportunity Funnel, has a broken Opportunity Funnel. Here is the set up for an Opportunity Funnel, which is out of the box from Microsoft. The Opportunity entity has a chart named “Sales Pipeline” which uses the “Pipeline Phase” field as it’s basis. It means this chart needs to reference a new custom field and in addition to the field name in the chart, anywhere the Pipeline Phase field is used in a view, form, workflow, etc., would have to be changed.
Is anyone else having this issue? Am I misunderstanding the new functionality here? We worked with Microsoft support and they told us we need to create the custom fields and I don't like this answer and I am hoping others have a better idea.
All responses (
Answers (
