#Salesforce Revenue Cloud22 discutindo

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 

Start Sync functionality programmatically?

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. 

#Revenue Cloud  #Ask An Expert  #Salesforce Revenue Cloud @* Salesforce Revenue Cloud *

What I'm building

A custom Lightning Web Component that embeds inside a cloned Product Configurator Screen Flow (the standard "Save As" third-party-configurator extension pattern — lightning__FlowScreen). The component calls the Product Configurator Business APIs directly via Apex HTTP callout (Named Credential auth, OAuth 2.0 Client Credentials Flow via an External Client App — not UserInfo.getSessionId(), which is rejected for interactive-UI sessions anyway).

Environment

• Developer Edition org with Revenue Cloud / Agentforce Revenue Management enabled (enableProductConfigurator = true)
• API version v64.0
• Not a scratch org, no source tracking — deployed directly
• Native in-app configurator UI works correctly for the running user; this is only about the headless REST layer

What works

POST /services/data/v64.0/connect/cpq/configurator/actions/configure — works reliably. Returns transactionContext.SalesTransaction[].SalesTransactionItem[], prices lines correctly, runs configuration rules, surfaces rule violations in messages. This endpoint alone is not gated.

What fails

Every other documented action in the same family returns a 403:

POST /services/data/v64.0/connect/cpq/configurator/actions/load-instancePOST /services/data/v64.0/connect/cpq/configurator/actions/get-instancePOST /services/data/v64.0/connect/cpq/configurator/actions/add-nodesPOST /services/data/v64.0/connect/cpq/configurator/actions/save-instance

Response body:

{  "errorCode": "FUNCTIONALITY_NOT_ENABLED",  "message": "[IHeadlessConfiguratorFamily]"}

(403 status, same error regardless of payload shape or whether the call carries a transactionContextId.) 

#Revenue Cloud  #Salesforce Revenue Cloud  #Lightning Product Setup Configurator  #CPQ  #Revenue Management System @* Salesforce Revenue Cloud *

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 *