1

We have a trigger on Opportunity, which always gets fired for any update in the child OpportunityLineItem records.

This works really well in all of my developer orgs, but in one of the client's UE(Unlimited Edition) org. The Opportunity trigger is only fired for a change in the following field:

"OpportunityLineItem->Unit Price"

Though the Opportunity trigger fires well, on any field change in OpportunityLineItem in my dev org.

What could be reason for this behavioural difference here ?

4
  • are that environments absolutely similar? including workflows and processes ? Jun 23, 2017 at 10:59
  • @AlexanderBerehovskiy, I tried to check it by deactivating all workflows/flows/process builders in the org but unfortunately not worked.
    – Pawan
    Jun 23, 2017 at 11:24
  • The client's price books may be set up and configured differently. They could also be using some kind of CPQ add-on like Apptus that would change the expected behavior.
    – crmprogdev
    Jun 23, 2017 at 12:17
  • @crmprogdev Checked the pricebook section as well but didn't find any change there.
    – Pawan
    Jun 27, 2017 at 4:12

1 Answer 1

3

This is the expected behavior,

Everytime you update the "UnitPrice" or "Quantity" standard fields on the OpportunityLineItem, the total opportunity amount or quantity get updated, hence triggering the opportunity's update trigger.

Any change on the other OpportunityLineItem fields (for example line description) has no effect on the parent opportunity therefore the opportunity update trigger is not fired.

You must check closely which fields you are updating on the line items. if these are custom fields you must look at triggers or processes related to your OpportunityLineItem object.

2
  • Yes, I thought the same that total price updates can only trigger the updates to the parent opportunity but I was wrong as when I checked it in the dev org. Every oli field updates (either it is unit price or description) firing the trigger on the parent opportunitg so still uncertain why it is not happening in the client's sandbox!
    – Pawan
    Jun 27, 2017 at 4:10
  • Anyway, now I resolved it in the sandbox via Opportunitylineitem trigger where I am performing blank updates to the parent opportunity to call parent opportunity trigger explicitly.
    – Pawan
    Jun 27, 2017 at 4:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .