Price Override in Project Operations | Part 2 [Understanding Change Amount effect]

Continuing from Part 1: Price Override in Project Operations | Part 1 [Inconsistent Price Update], let’s look at the Pricing.

  1. When you entered $250 for the Price Per Unit – you assumed it will update the price to $250 from $225

  2. And what you got it this – $475


Here’s the catch!

Although the wordings of the field convey that it’ll be updated to the absolute price you entered, rather it “added” to the existing Price!!
Hence, 250 + 225 = 475.

So, don’t make the mistake of assuming it’s asking for ‘new price‘, it’s actually asking you ‘how to much to increase or decrease the price by

Hope this was useful!

Hope this was helpful!

Thank you!

Price Override in Project Operations | Part 1 [Understanding Change Amount effect]

So, often times if you are working on Project Contracts, you must have encountered this button which creates a separate Price List for the Quote itself – Project Contract Price List Defaulting Behavior in Project Operations

But here’s how to track and find what happens to these Price Lists and what Price Override levels are –

Creating Price Overrides

  1. Here’ where you can find the Prices to be overridden on a Price List level –


  2. Now, when a new Quick Create form is created, you can fill in the details for either the new Price or the % and the Scope.

  3. Now, when you add the Price Per Unit, also notice that there’s a Scope field as well. Notice the types of records for the Scope defines at what level should this take effect.


  4. Let’s select an Account and save.

  5. Now when I save the record, notice that the Price is added differently.


    So, let me demystify this Part 2 of this post here: Price Override in Project Operations | Part 2 [Understanding Change Amount effect]

Hope this was helpful!

Thank you!