* Salesforce Revenue Cloud *

Hello everyone,

We are using Salesforce Revenue Cloud Advanced Product Configurator with Set Up Configuration Rules with Business Rules Engine enabled.

Our requirement is:

If the account associated with a quote already has an Asset for INTERNET HOME 50/5MBPS, the Product Configurator must require the user to add INTERNET HOME ONLINE OFFER.

I created the following Product Configuration Rule:

• Rule Scope: Transaction
• Condition field: AssetProduct
• Operator: Equals
• Value: INTERNET HOME 50/5MBPS
• Action: Require
• Required product: INTERNET HOME ONLINE OFFER

AssetProduct is available for selection in the rule designer. However, when I validate the rule, I receive this error:

“We couldn’t find a Context Tag corresponding to a Line Item. Specify a valid Line Item Context Tag and try again.”

As a diagnostic test, I duplicated the rule and changed only the condition field:

AssetProduct → Product

The rule then validated successfully. Therefore, the validation failure appears to be specifically related to AssetProduct or its context configuration.

Could someone please confirm:

1. Is AssetProduct officially supported as a condition field in Product Configuration Rules executed by the Business Rules Engine?
2. Or is asset-based evaluation supported only through Constraint Models and the Constraint Rules Engine?
3. If AssetProduct is supported with BRE, what exact configuration is required?
   • Must we extend AssetContext__stdctx?
   • Must the extended Asset Context be selected under Revenue Settings → Set Up Asset Context for Product Configurator?
   • Which attribute, context tag and object-field mapping must be configured for AssetProduct?
4. Does AssetProduct evaluate all relevant Assets belonging to the quote’s Account, or only an Asset explicitly selected or included in the current transaction?

I have attached a screenshot of the rule configuration. Any confirmation from someone who has successfully used AssetProduct in a BRE configuration rule would be greatly appreciated.

Thank you. 

Hi all,

I’m running into an issue with the Billing Batch Scheduler / Billing Schedule processing.

I have a record-triggered Flow on Billing Schedule for After Insert and After Update. From the flow, I am performing the required DML through an asynchronous/scheduled path approximately 5 minutes after the record transaction

, rather than performing the update immediately in the same transaction. I have automation in Invoice and Invoice Line in a flow in before and after save both.  

When the billing batch runs, multiple records are failing and I see the following errors under Revenue Transaction Error Logs

: 

I’m also seeing:

There are multiple Revenue Transaction Error Log records with the same/similar errors.

Has anyone encountered the attempt to save object not in TransactionEntityObjectMap error before?

I’m trying to understand:

1. What exactly does TransactionEntityObjectMap refer to in Salesforce Billing / Revenue Cloud processing?
2. Even though my DML runs asynchronously around 5 minutes later, could it still conflict with Billing Batch Scheduler processing?
3. Could the Billing Schedule or related records still be locked or considered part of an active Revenue transaction when the asynchronous flow runs?
4. Is there a recommended delay or automation pattern for updating Billing Schedule/related records after billing processing?
5. Is this likely a Salesforce internal transaction-state issue, or is there something specific I should avoid updating from the flow?
6. Has anyone found a workaround or resolution for this error?

Any insight into the exact root cause of this error and the recommended resolution would be greatly appreciated.

Thanks!

I'm testing Agentforce Revenue Management (Revenue Cloud) in a Salesforce trial org (Enterprise Edition, API Version 67.0) and have three related questions. 

Background

For a custom implementation we store a very large volume of non-lifecycle customer records in the standard Asset object. We chose Asset because, in our testing, Asset records themselves do not count toward data storage limits (Setup → Storage Usage shows no data storage use for them), and we want to keep that behavior.

1. AssetActivity availability and storage

In this Revenue Cloud org, inserting plain Asset records through the API, with no order and no lifecycle call, creates AssetActivity and AssetActivityFieldChange records, and data storage rises. 

I see no related flows or Apex triggers, nothing in debug logs, and no toggle in Setup → Asset Settings. The AssetActivity object is

, so something org-specific seems to control it. 

2. Planned Asset record type

We plan to add a record type on Asset. One would behave as the standard Revenue Cloud asset, and the other would hold the non-lifecycle records created through an integration (HasLifecycleManagement = false). We want to understand the impact on

if a new record type is created on Asset. 

3. Storage behavior of Asset

We want to confirm the assumption our design relies on.

Questions:

1. Is it correct that Asset records do not count toward data storage? Is that documented and supported, or could it change?
2. Which feature, license or permission set license makes AssetActivity and AssetActivityFieldChange available in an org? Why do some Revenue Cloud orgs have the object and others don't?
3. What creates AssetActivity records when an Asset is inserted or updated? Is it platform-native?
4. Can creation be disabled, or excluded for a record type, user or API path? Can the records be updated or deleted to recover storage?
5. Does Asset Lifecycle Management (order activation, amend, renew, cancel, and the Asset Action, Asset Action Source and Asset State Period records) depend on a particular Asset record type? Does it take the record type from the running user's default?
6. If we add a record type on Asset, are non-lifecycle-managed assets ignored by lifecycle processes, APIs, flows and screens? Is keeping both kinds of record on Asset supported?
7. Is there a recommended pattern for storing very high volumes of non-lifecycle customer records in Revenue Cloud without consuming data storage?

Thanks!

Hi everyone,  

In Revenue Cloud Product Configurator, the attribute category tabs appear in alphabetical order. For example, "Fabric / Leather" shows before "Finish", but we need Finish first and Fabric / Leather second

.  

What we tried: 

• Setting Sequence on the Product Classification Attributes and the Product Attribute Definitions. This changes the order of attributes within a tab, but not the tab order.
• Renaming the category (e.g. "Upholstery"). This works, but we'd prefer to keep our original category names.

Questions: 

1. Is there a field or setting that controls the display order of attribute categories (tabs)?
2. Can this be set in the Product Configurator Flow (Product Attributes component)?
3. If not, is this on the roadmap, or does anyone have a workaround other than renaming?

I am trying to generate the document using docgen, without using any data mapper. I want to show horizontally repeating rows instead of vertical repeating rows. For example, if my data is like following - 

1. Product 1 - 25000 

2. Product 2 - 30000 

3. Product 3 - 32000 

so instead of showing it like - 

Product 1 | 25000 

Product 2 | 30000 

Product 3 | 32000  

i want to display like in a table- 

Product 1 | Product 2 | Product 3 

25000       | 30000       | 32000 

can we achieve this? or not? 

@* Salesforce Revenue Cloud *

#Revenue Cloud  #Document Generation