Loading

Revenue Cloud: PricingTermCount on quote line item defaults to 1 until a field is manually edited

Publish Date: May 26, 2026
Description

This article explains why the PricingTermCount field on a Revenue Cloud Quote Line Item [PricingTermCount] is set to 1 on the first save of a multi-year quote, and how to force a correct recalculation. Customers describe this as: "When we configure a Quote using the Start Date and End Date, the PricingTermCount is always set to 1 even though the Start date and end date differs 3 years, until and unless anything is updated, then the PricingTermCount is set to correct value" and "In Revenue Cloud, as soon as I add a product with Product Selling Model = Term-based and change the subscription duration in the Quote Line Transaction Editor, the end date is not updating — only updates once I remove the end dates individually." Trigger conditions: a Quote Line Item is created from a term-based Product Selling Model [ProductSellingModel], the Start Date [StartDate] and End Date [EndDate] on the Quote span more than the product's default pricing term, and the line is saved before a second pricing pass runs. Affected scope: Revenue Cloud (Core) on Enterprise, Unlimited, and Developer editions where Transaction Management is enabled, Summer '24 release and later. Term-based pricing calculations and any downstream automation that reads PricingTermCount at the time of the first save are affected; bundle products, ramp deals, and amendments to ramped lines exhibit the same recalculation timing.

Resolution

Use the steps below to recalculate PricingTermCount on an affected quote line and to prevent the issue on new quote lines.

Cause 1: PricingTermCount was not recalculated after the multi-year date range was applied
1. Open the affected quote in Revenue Cloud and launch the Quote Line Transaction Editor for the Quote [Quote] record.
2. Locate the Quote Line Item [QuoteLineItem] where PricingTermCount [PricingTermCount] shows 1.
3. Clear the End Date [EndDate] field on that quote line item, then click Save. Wait for the "Re-calculating" indicator at the top of the Quote page to disappear (the recalculation is asynchronous and typically completes within a few seconds).
4. Refresh the page. Confirm PricingTermCount now reflects the full term derived from Start Date [StartDate] and the product's selling model.
5. Reopen the Quote Line Transaction Editor, set the End Date [EndDate] back to the required value, and click Save. The recalculation now runs against the corrected term and PricingTermCount remains correct.

Cause 2: End Date is not updating when Subscription Term or Pricing Term Count is changed in the Transaction Line Editor
1. Open the Quote Line Transaction Editor for the affected Quote [Quote].
2. For each affected Quote Line Item, clear the End Date [EndDate] field.
3. Update the Subscription Term [SubscriptionTerm] or PricingTermCount [PricingTermCount] field to the desired value and click Save.
4. With End Date blank at save time, the calculator derives End Date from Start Date [StartDate] plus the new term. If End Date is populated at save, the calculator treats End Date as authoritative and ignores Subscription Term.
5. Refresh the page after the "Re-calculating" indicator clears.

Cause 3: Bulk update is required across many quote lines
1. From Setup, go to Setup > Object Manager > Quote Line Item [QuoteLineItem] > Fields & Relationships and confirm End Date [EndDate] and PricingTermCount [PricingTermCount] are exposed on the page layout used by your sales reps.
2. Build a Flow on the Quote [Quote] object that, on update of Start Date [StartDate] or End Date [EndDate], updates the related Quote Line Items by writing both Start Date [StartDate] and End Date [EndDate] in the same Update Records element. Updating both date fields together causes the calculator to treat the change as a term change rather than a coverage shift, which preserves the intended dates and forces PricingTermCount to recalculate.
3. Activate the flow and reopen one of the affected quotes to trigger a recalculation.

Verification
Confirm the issue is resolved by opening a previously affected quote, verifying that PricingTermCount [PricingTermCount] on each Quote Line Item matches the term implied by Start Date [StartDate] and End Date [EndDate] (for example, 36 for a 3-year term-based product) without any further manual edit, and that the Net Total Price on the Line Item Details tab reflects the multi-year term.

Knowledge Article Number

005385110

 
Loading
Salesforce Help | Article