[GAURANG PATEL]

It seems we could use Quote Line Groups, which would allow different dates for each line item.

[GAURANG PATEL]

Hi Gilles, We’ve decided to use a lookup to a custom Address object to represent the delivery location. Since we have around 10,000 print products, we’ll explore the two options you mentioned.

Really appreciate your quick response. thanks again!

[GAURANG PATEL]

Using separate quotes for Cancel and Replace introduced additional complexity into our back-office order processing. Our downstream systems include Oracle PeopleSoft for billing, a custom-built fulfillment system, and a variable compensation platform—all of which rely on orders to receive line item data.

We publish a platform event containing the Order ID to our middleware, which then queries Salesforce to retrieve the order header, line items, and other necessary details.

Initially, we submitted Cancel and Replace orders separately and in sequence. However, this approach caused issues—often the cancel order would process successfully, while the replace order failed due to system or technical errors, leading to customer-facing disruptions.

To address this, we revised the process to combine both cancel and replace orders into a single platform event. The middleware now treats them as one transaction, ensuring downstream systems process the cancel line items first, followed by the replace line items. This change has significantly improved reliability and reduced errors.

[GAURANG PATEL]

Hi Gilles,

We’re currently using the Cancel and Replace package for amendments, but we had to customize it extensively since some of our use cases weren’t supported out of the box.

Our business relies heavily on multi-year deals, and we use MDQ (Multi-Dimensional Quoting) products. One issue we encountered is that during Cancel and Replace, the system defaults the start date on the replacement quote to today’s date. However, in our use case, sales reps often need to future-date the start date into the next segment of a multi-year contract. The system wasn’t syncing that new date back to the cancel quote, so we had to customize the package to delete the original cancel quote and recreate it with the appropriate future-dated segment.

Another challenge is around sales negotiations. Reps often don’t know upfront what the amendment will be—it could be an upsell effective immediately, an upsell effective in a future segment, or a renewal. We’ve built support for all three scenarios, which led to significant customization.

Due to this heavy customization, we’re currently limited to adding no more than 170 products per quote.

We’re now exploring enabling the Large Quote Experience, but doing so would alter the layout of the segmented line editor, which presents additional challenges

[GAURANG PATEL]

Gilles, After re-enabling the triggers, if I update a field on the Quote header that’s part of the <em data-start=”168″ data-end=”188″ style=”font-family: inherit; font-size: inherit;”>Calculating Fields fieldset, that will trigger a recalculation of the entire quote. correct?

Also, just to confirm—Product Rules won’t execute if triggers are disabled, correct?

[GAURANG PATEL]

Thanks Gilles, This is really helpful