Microsoft Dynamics CRM (Archived)

Need to update field based on active stage in Business Process Flow

(0) Share

Report

Posted on by wperkinson3

I have a business process flow for an opportunity that consists of the following stages

Categories

-Qualify

-Develop

-Propose

-Close

I have created a business process that looks at the active stage/category to set a field on the form.

3817.BusinessRule.jpg

I move through the stages within the Business Process Flow, but the business rule does not update the probability field.

If I save/close the record and reopen it, the probability field updates upon open. Why does the field not update real-time as I move through the stages?

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (2)

Michel Gueli 982 on at

Like (0)

Report

Check the scope of your business rule.

Was this reply helpful? Yes No
Verified answer

John Clark 400 on at

Like (0)

Report

An alternative approach would be to replace your business rule with a synchronous workflow linked to the business process flow entity. Set the workflow to trigger when the process is applied and on the change of the Active Status field. You can then update the probability field on the opportunity. The probability field will update on the form immediately.

If the workflow spans multiple entities you should check that it is linked to an opportunity before attempting to update the opportunity.

Was this reply helpful? Yes No
wperkinson3 2 on at

Like (0)

Report

I am trying to add the workflow to the stage as I enter it, but it will not allow me to select it.

Was this reply helpful? Yes No
Verified answer

John Clark 400 on at

Like (0)

Report

With my suggested approach you don't need the business rule. You just need a real-time workflow, like below:

Was this reply helpful? Yes No
wperkinson3 2 on at

Like (0)

Report

John,

Thank you.

We have customized the Business Process flow for Opportunity. Is there a way using your method to check the "Displayed" name of the step?

Regards,

Will

Was this reply helpful? Yes No
John Clark 400 on at

Like (0)

Report

The "Process Stage Name" field on the "Active Stage (Process Stage)" entity is the displayed name. It's a text field, so not so nice to work with, which is why I prefer the Stage Category, which is a Global Option Set.

Cheers,

John

Was this reply helpful? Yes No
wperkinson3 2 on at

Like (0)

Report

Thank you for the feedback. I will attempt to setup the real-time workflow this afternoon based on the categories.

What are you using as the fields under start when process changes?

Was this reply helpful? Yes No
John Clark 400 on at

Like (0)

Report

Just the Active Stage (activestageid) field, which is the lookup to the Active Stage (Process Stage) entity. This changes each time the stage changes.

Cheers,

John

Was this reply helpful? Yes No
wperkinson3 2 on at

Like (0)

Report

John,

When I add the check to see if the process flow is linked to the Opportunity record, I see the following. I does not reflect what your screen showed with the "Related Opportunity". I wish to make sure I have this correct before I build in the remaining logic.

Thank you,

Will

Was this reply helpful? Yes No
John Clark 400 on at

Like (0)

Report

You've got the right thing.

The difference in naming is a quirk/legacy of the previous iteration of how Microsoft implemented business process flows. If you have a look at the N:1 relationships of the out-of-the-box "Opportunity Sales Process" you'll see that the opportunity relationship has field name "Related Opportunity", while in any new business process flows, it just comes out as "Opportunity".

[In the default "Lead to Opportunity Sales Process" it's called "Opportunity id", just to be consistent.]

Cheers,

John

Was this reply helpful? Yes No