0

On Opportunity Object i have 3 custom currency fields called

1) Product Amount 2) Support Amount 3) Maintainence Amount

Total Value of these 3 fields is reflected on formula field called Deal Value, process builder flow fires once deal value is generated and it updates Amount field which is standard field.

This is done because enterprise reporting is conducted on Amount Field rather than deal value.

Now i being asked to automate renewal opportunities, I have created one using process builder here are the details

enter image description here

i have set field values for

1) Product Amount 2) Support Amount 3) Maintainence Amount

Using field reference type.

Also I have unchecked option under

Advanced Do you want to execute the actions only when specified changes are made to the record?

This is working perfectly fine but process is creating TWO records instead of ONE. here is the screenshot where it has created two records

enter image description here

I am suspecting the first process of deal value updating amount value is impacting this one and leading to creating two records, but i am not sure of this

For the record, these are the ONLY TWO processes which are currently running in my organization

Any Help is appreciated

Kind Regards Prashant

  • what are the entry conditions for the decision block? perhaps it is being executed twice -- something you could see from the debug log. Presumably, you only want the renewal opportunity to be created when the Oppo goes to closed won -- and hence you would want Do you want to execute the actions only when specified changes are made to the record? to be true so the decision block only fires the first time the oppo becomes closed won and not on subsequent changes to that oppo – cropredy Apr 5 at 17:15
0

You can run into problems based on your selections for:

  • When to Start This Process
  • Criteria for Executing Actions

If you do not think this through, you can end up with behaviour that was not intended.

Based on your selections, it seems like the action to insert a new Opportunity will be executed each time an Opportunity is updated and its stage is Closed-Won.

Consider the following example:

I have an Opportunity that is already Closed-Won and I update the name and click save. In this example, your process will be fired, criteria is met and a new Opportunity is inserted.

Consider defining the criteria for the Action to meet your specific use case. So if you are looking to ONLY fire this action when the stage is changed to Closed Won, consider doing the following:

enter image description here

Also, As @cropredy stated, you probably should check the Do you want to execute the actions only when specified changes are made to the record? because it seems like you only want to update the actions when the Opportunity is changed to the stage Closed-Won.

I would also suggest that if you currently you merge the two Opportunity processes into a single one. This gives you other advantages:

  • Controlling order of execution of your actions
  • Streamlining similar logic in a single place (easier to maintain)
  • Cleaner Organization (of your Org)

    Should you start developing more complicated logic in the form of triggers etc., If you have too many processes firing this makes it very difficult to debug and follow all the actions that are firing when you insert/update a record.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.