* Salesforce Revenue Cloud *

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!

@Hanna Homb Reistad You can try configuring Product Code as a searchable field in the product index instead of updating Product Name to include Product Code.

Please follow these steps:

1. Click Create Full Index under 'Use Indexed Data for Product Listing and Search' setting.
2. Open the Manage Fields & Attributes tab and click Edit.
3. Locate the Product Code field and enable the Searchable option and save.
4. Navigate to the Indexes tab and select Rebuild Index > Full Index Rebuild.
5. Wait for the rebuild to complete successfully.

After the index is rebuilt, test the search again in the Sales Transaction Line Editor.

Note:

Based on my experience, when searching by Product Code, try entering the complete product code rather than only a partial code. Unlike product name searches, partial-code searches may not always return the expected results. 

Please refer to this official salesforce documentation: Configure Searchable Fields & Attributes

Hope this helps! 

Hi Cheryl, I haven't seen Quote Line Group offered as a primary object in report types either. Two workarounds that usually get you there: 

1) Create a custom report type on Quote Line Items, then use "Add fields related via lookup" to pull in the group's fields (name, subtotal, etc.). That gives you line-level reporting you can group by Quote Line Group. 

2) If you need group-level totals, use a record-triggered Flow to copy the key group values onto Quote Line Item or Quote fields, and report on those. 

For heavier analysis, CRM Analytics can also pull the object in through a dataset recipe. Hope this helps!

@Rachel Linder amend copies every active subscription onto the quote. There is no native filter on that Client field, and the Amend Subscriptions list will not start you from a subset. That is why the editor, the opportunity sync, and the approval all choke.

Setting quantity to 0 is a cancellation. Deleting the quote line leaves the subscription as it is. That is why your delete workaround is the right one. Automate it. Right after amend, a flow or Apex deletes every amendment line whose Client is not the one they picked, before the quote is primary and before approval. Do that before the sync, or the opportunity products are already created.

The lasting fix is one contract per client. A reseller account with every end client on the same contract will always amend the whole set. Split those subscriptions onto contracts by client and the amend only loads that client.

@Tushar Konde That message means the line editor couldn't find a usable derived price record for the product you just added. A derived product doesn't price from a normal price book entry. It prices from a derived price that points at a contributing product.

The usual miss is adding the derived product on its own. The contributing product has to already be on the quote, and the derived price record has to use that product as its source, on the same price book and selling model as the quote. If any of those don't match, the lookup comes back empty and you get Derived Price Record with nothing after it.

Check the derived price record first, then add the source product, then the derived one. If the record is right and the source is already on the quote, the pricing procedure on that quote isn't running the derived price element, so the line still has nothing to price with.

Hi Serhii,

The validation message is the useful part. A Product Configuration Rule on the Business Rules Engine is looking for a line-item context tag. Product validates because it's on the transaction line. AssetProduct showing up in the condition dropdown doesn't mean that tag is mapped as a line item, which is why you get "We couldn't find a Context Tag corresponding to a Line Item."

Rules that need to see assets the account already owns are what the Constraint Rules Engine is for, after asset context is set up for the configurator in Revenue Settings. Standard configurator with the Business Rules Engine stays on the transaction. Advanced configurator is the one that evaluates constraints across that wider context.

I wouldn't keep forcing AssetProduct through a BRE transaction rule to satisfy the dropdown. The field being selectable isn't the same as the context definition knowing it. I also can't give you a tag mapping that turns AssetProduct into a supported BRE line-item condition, because that isn't documented. If the rule has to require a product because the account already has an asset, build that as a constraint with asset context, not as a second copy of this rule.