I have a custom number field called Project Duration, which stores the duration in months. Whenever a value is entered in this field, the End Date on the Quote Line Item (QLI) should be recalculated based on the Start Date + Project Duration.
For example, if the Start Date is 1st January 2026 and the Project Duration is 12 months, the End Date should be 31st December 2026.
I tried implementing this using a Flow. Although the End Date is calculated correctly, the pricing calculation appears to lag by one change. For example, when I update Project Duration to 12 months, the price is calculated using the previously entered duration. If I then change Project Duration to 24 months, the pricing is recalculated based on 12 months instead of 24 months. Can someone please help.
Hi Preeti, good questions.
On option 2: yes, map Project Duration as an input to the pricing procedure, but don't put it straight into Pricing Term Count. That count is measured in the product's term unit, so derive it:
Monthly term: Pricing Term Count = Project Duration
Annual term: Pricing Term Count = Project Duration / 12
That's why your annual line shows 12 months between the dates but a term count of 1. Both are correct for an annual unit.
On option 3: since Project Duration is already in the Sales Transaction context mapping, check that the pricing procedure actually reads it from the context, and that the mapping points at the QLI node, not the Quote header. If the procedure still uses the stored field value, you'll keep seeing the price one change behind.
If you share how the term unit is set on the product, I can suggest the exact element to use. Hope this helps!
