* Salesforce Revenue Cloud *

@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.

Hi Ganesh,

I don't have a public doc that defines TransactionEntityObjectMap. That name is internal to the billing transaction. What you can use is the Error Message and the related record on the Revenue Transaction Error Log, plus the status on the invoice batch run.

A billing batch run writes those logs when invoice generation fails, and a failed billing schedule can sit there until you use Recover on the invoice batch run. Recover puts the schedule back to Ready for Invoicing so a later run can pick it up.

Your Invoice and Invoice Line flows are the part I'd look at first. Before-save and after-save automation on those objects runs while the batch is saving the invoice. Salesforce's billing notes say to test flows on invoices and invoice lines during an invoice run for that reason. A flow on Billing Schedule that updates the schedule, even on a 5 minute scheduled path, is not a lock check. The batch often runs longer than 5 minutes, and a later update can still land while that schedule is in the run.

One documented cause of INVOICE_GENERATION_FAILED is a custom field on Invoice or Invoice Line marked required. The batch API doesn't fill custom fields, so the save fails and the log looks like an unknown exception. Populate those after the invoice exists, and don't make them required.

In a sandbox, read one log's Error Message in full, then deactivate the Invoice and Invoice Line flows and generate a single invoice from one billing schedule. If that one succeeds, the flow is in the transaction, and a longer delay won't clear it.

Hi Rajdeep,

Asset is not on the short list of objects Salesforce leaves out of data storage. Accounts, contacts, opportunities, cases, and a few others are. Asset is not one of them. A trial org storage page showing zero is not something I would build a design on. It lags, and it is not a documented exemption. After a real volume of inserts, check Storage Usage again before you commit to this.

AssetActivity and AssetActivityFieldChange show up in orgs where the fuller asset lifecycle tracking got turned on. That is why the object exists here and not in your other Revenue Cloud orgs. It is platform behavior, not a flow or a trigger you can find. A plain API insert is enough to write those rows, and those rows are what push storage up. I have not seen a per-record-type switch that stops it.

Lifecycle does not depend on an Asset record type. Amend, renew, and cancel follow HasLifecycleManagement and the asset action records. Adding a record type changes layouts and the default type on create. It does not hide the other rows from lifecycle screens. A user whose default record type is the integration one can also send new assets to the wrong type. Order activation still builds the lifecycle asset on its own path.

Keeping both kinds of record on Asset only works if the integration rows are actually HasLifecycleManagement = false, and you accept that anyone who can see Asset can see both. It will not keep those rows out of storage, and it will not stop AssetActivity if that tracking is on.

For a very large set of non-lifecycle records, I would not put them on Asset. A big object, or something outside the org, is the volume pattern. Asset is for the records lifecycle is supposed to manage.

Thanks for taking the time to answer @Bhavin Patel and @Ben Stokes

!  

This guide seems related to CPQ and not Agentforce Revenue Management.  

As for,  

, I'm using  "Indexed Data for Product Listing and Search", so then Product Field Search won't work.  

"Error

To enable Product Field Search, you must first disable Indexed Data for Product Listing and Search." 

I ended up updating the Product Name with Product Code to achieve desired result.  

/Hanna 

@Deepak Sachdeva

Thank you for the advice. 

Here is where I am and seem to can proceed. 

I have extended the ProductDiscovery Context 

I have added the Attribute to the Catalog Node 

• BranchID, Input/output, String
• I have given it a tag

When I attempt to map the Catalog (left side) to the Product Catalog (right side) I get this error message: " 

You can't update an inherited node mapping that already has an mapping." 

 If I try to go from field to field this is the error I get: " 

Ensure that you map attributes to the field of same sObject that’s mapped to its corresponding node." 

Thoughts?