#Salesforce Revenue Cloud20 discussing

Hi All,  

The standard out-of-the-box Start Sync button in RCA. When a user clicks it, it:

• Sets the Quote as the Synced Quote on the associated Opportunity
• Populates the standard OOB Quote/Opportunity sync fields and links
• Syncs the Quote Lines to Opportunity Products

For our cancellation process, I’d like to automate this behavior. Instead of requiring the rep to manually click Start Sync, the cancellation automation should automatically sync the cancellation Quote to its associated Opportunity and then allow the Opportunity to be closed as part of the same process.

The issue I’m running into is that the fields involved for syncing on the Quote/Opportunity sync don’t appear to be available or updateable through Flow. From what I can tell, Start Sync is invoking a standard Salesforce/RCA sync page or process rather than simply updating fields.

Has anyone successfully invoked the same

Specifically, I’m wondering whether there is a supported way to:

• Trigger the standard RCA Quote → Opportunity sync from Flow
• Invoke it through Apex, an API, or another automation mechanism

I’d prefer to leverage the standard RCA sync functionality if possible so that the automated cancellation process behaves exactly the same way as a rep clicking Start Sync.

Any guidance on the supported approach or the underlying API/process that Start Sync

invokes would be greatly appreciated. 

Hi everyone,

I’m working with the Sales Transaction Line Editor (STLE) in Salesforce Revenue Cloud and would like to know if it is possible to add a custom button/action at the row level for each transaction line.

For example, I would like to have a custom button or action available on each individual row in the Sales Transaction Line Editor that can trigger custom logic.

Has anyone implemented something similar? If yes, could you please share the recommended approach or any documentation/examples for extending or customizing the row-level actions in STLE?

Any guidance would be greatly appreciated. Thank you! 

Hi everyone, 

Appreciate advise on implementation of the following requirements in revenue cloud. 

The customer sells cloud solutions as bundled offerings. For example, a Server bundle consists of components such as a Virtual Machine, Storage Capacity, and other optional add-ons. Each component has its own set of attributes, forms an individual SKU, and is priced using attribute-based pricing. 

The customer wants to model these offerings as bundles where the parent bundle product serves only as a logical container and is not an actual sellable product. As such, no price should be assigned to the parent bundle. Instead, the business expects the price displayed for the parent bundle to be the aggregated total of all its child components. 

We have the following questions: 

Is there an out-of-the-box capability to synchronize quote line items to the Opportunity while excluding the parent bundle product? Since the parent is only a container, the business does not want it to be created as an Opportunity Product. 

Currently, the TotalPrice on Quote includes both the TotalPrice of the bundle product and all of the child components, resulting in double counting. Is there a standard or recommended approach in Revenue Cloud Advanced to ensure the quote total reflects only the aggregated value of specific line items e.g I want to exclude the aggregation on the bundle? 

Thank You!

 I am running into an issue where a one-time product component inside a bundle is dropping off during the contract renewal process in Agentforce Revenue Management (ARM) / Revenue Cloud.

Scenario

• We create a renewal from an existing contract.
• The bundle contains both recurring and one-time products.
• During the renewal process, the one-time product remains part of the bundle on both the Renewal Quote and the Renewal Order, which is the expected behavior.

The Problem

• The issue appears after the Renewal Order is activated.
• The new Renewal Contract is created successfully, but the one-time product is missing from the contract structure. After investigating, I found that the platform does not create an AssetContractRelationship (ACR) record for the one-time asset on the new contract, even though the ACR was created correctly for the original contract.

What we have already verified/troubleshot:

1. Asset Generation: An Asset record was successfully generated for the one-time item from the initial order.
2. Lifecycle End Date: The Lifecycle End Date on the specific one-time Asset record is Blank (it is not expired).
3. Asset Records: Both Asset State Periods and Asset Action Source records are fully available and populated.

Has anyone experienced this behavior? 

It looks like the contract activation process is excluding assets associated with a One-Time Product Selling Model Category when creating the Renewal Contract, even though the product is still part of the Renewal Order and bundle. 

Is there a known limitation, configuration, or mapping rule that controls whether an AssetContractRelationship is created during contract activation? Are there any fields on the Asset, Order Item, or Product Selling Model that I should verify? 

I'd really appreciate any insights or workarounds. Thanks in advance! 

@* Salesforce Revenue Cloud * 

I'm looking for guidance on the recommended modeling approach in Revenue Cloud  for configurable furniture bundles.

Scenario

We have a bundled furniture product that consists of multiple child products. (see attached for bundle details) 

For example:

Parent Bundle

• Desk

The bundle is available in four finishes:

• Espresso
• Dark Walnut
• Gray
• Cherry

Each finish represents a different set of child SKUs.

For example:

Gray Finish

• Desk Shell → Gray SKU
• Return Shell → Gray SKU
• Pedestal → Gray SKU

Dark Walnut Finish

• Desk Shell → Walnut SKU
• Return Shell → Walnut SKU
• Pedestal → Walnut SKU

The bundle structure remains identical—the only thing that changes is the SKU assigned to each child component based on the selected finish.

The product hierarchy and option mappings are maintained in our PIM and synchronized into Salesforce.

Goal

When a seller configures the bundle and selects Gray, I want Revenue Cloud to automatically substitute all of the child SKUs with the corresponding Gray SKUs.

Likewise, selecting another finish should automatically replace all child SKUs with the matching variants.

My Question

Is Constraint Builder intended to solve this type of SKU substitution, or is there another recommended approach in Revenue Cloud Advanced?

Some possibilities I'm considering are:

• Constraint Builder
• Product Variants
• Product Configurator
• Bundle Option Groups
• Variant Resolution
• A custom mapping object driven from PIM
• Another recommended design pattern

I initially expected to associate Constraint Models at the Product Class level, but the Product Class selection in Constraint Builder is disabled in my org. Salesforce Support indicated this functionality is not currently available.

For organizations with highly configurable products, what is the recommended architecture for maintaining one logical bundle while automatically substituting the appropriate child SKUs based on a selected finish or color?

I'm looking for the most scalable, metadata-driven approach that minimizes custom development and leverages standard Revenue Cloud capabilities wherever possible.