Skip to main content
Temas#Revenue Management System

#Revenue Management System12 debatiendo

Formular una pregunta...
Dhaval Shah (Salesforce Analyst en Magnum Cementing Service Ltd.) preguntó en #Salesforce Developer
Hoy, 16:58
Salesforce CPQ to Agentforce Revenue Cloud migration

Hi Everyone, 

 

I would like to get some clarification on the best approach for migrating from Salesforce CPQ to Agentforce Revenue Cloud. 

 

Specifically, I’m trying to understand how the licensing and org setup work during the migration. If we migrate everything from our existing Salesforce CPQ solution to Revenue Cloud, would we need to continue paying for both the existing CPQ org/licenses and the new Revenue Cloud licenses during the transition, or would we only need to pay for the Revenue Cloud licenses? 

 

Also, how does Salesforce typically handle the transition period between CPQ and Revenue Cloud? Is there a recommended approach or migration strategy that allows us to avoid paying for both solutions for an extended period? 

 

If anyone has gone through a CPQ-to-Revenue Cloud migration or has experience with the licensing side of it, I would really appreciate your insights. 

 

Thanks. 

 

#Salesforce Developer  #Agentforce  #Revenue Cloud  #Salesforce Revenue Cloud  #Revenue Management System  #Salesforce CPQ & Billing  #CPQ

Escribir una respuesta...
0/9000
barkavi viswanthan (Senior Software Engineer en Tech Mahindra) preguntó en #Revenue Cloud
Hoy, 13:10
Revenue Cloud -Products are not showing in browse catelog

Hello Community,

I recently created a new Revenue Cloud Developer Org and completed the initial Revenue Cloud setup (https://trailhead.salesforce.com/promo/orgs/get-started-revenue-cloud) . However, I'm facing an issue with Browse Catalog.

When I open Browse Catalog, the category hierarchy is displayed correctly, but no products are visible under any category.

I have already verified the following:

  • Categories and hierarchy are created correctly
  • Products are active
  • Product Category relationships exist
  • Product Selling Model Options are configured
  • Standard Price Book entries are created
  • Rebuilt the Product Index using Full Refresh
  • Performed Pricing Synchronization
  • Tested with System Administrator access

What's interesting is that even the standard/sample products that come with the Revenue Cloud Developer Org are not visible in Browse Catalog.

Has anyone encountered this issue before? Are there any additional setup steps, publication steps, catalog activation requirements, or indexing processes required to make products appear in Browse Catalog?

Any guidance would be greatly appreciated.

Thank you! 

 

#Revenue Cloud  #Salesforce Revenue Cloud  #Salesforce Developer  #Revenue Management System

 

 

#TrailblazerCommunity  #Trailhead

Escribir una respuesta...
0/9000
Magdeson Gonçalves Nonato (Salesforce Administrator en Grupo TAAK LTDA) preguntó en #Trailhead Challenges
10 sept, 21:18
Discover and Configure Products

Hello, 

 

I am trying to complete this

module,

and I am getting the following error: 

We can’t find the quote Office Supplies. Make sure you create the quote for the EdgeMX account. 

 

However, the quote has been created for the correct account and includes the products; I followed the content and challenge steps correctly. 

 

I am also using a special Developer Edition org with Agentforce Revenue Management. 

 

Can anyone help? 

Thanks in advance. 

 

 

#Trailhead Challenges  #Trailhead  #Revenue Cloud  #Salesforce Revenue Cloud  #Revenue Management System

Screenshot at Sep 10 18-17-49.png
Screenshot at Sep 10 18-18-15.png
5 respuestas
  1. Magdeson Gonçalves Nonato (Grupo TAAK LTDA)
    22 sept, 12:19

    Hello, 

     

    I opened a case directly with Salesforce; for it to work, the quote needs to be created from the opportunity record. 

     

    Thanks.

Escribir una respuesta...
0/9000
Swati Malkar (Software Engineer en Amdrodd Technologies) preguntó en #Sales Cloud
4 sept, 12:33
Anyone else struggling with Spiff/Incentive Compensation in native Salesforce? Mine keeps breaking on backdated deal changes- how are you handling it?

The payout happened in the March commission run (that's when it was calculated and paid).

The deal's close date now shows February (because it was edited/backdated after the fact).

So there's a disconnect between when the money was actually paid (March) and what period the deal currently says it belongs to (February). 

 

#Sales Cloud  #Revenue Management System  #Revenue Cloud  #Salesforce Revenue Cloud

2 respuestas
  1. Asim Ansari (Intellectual Clouds)
    4 sept, 13:30

    Hi @Swati Malkar

     

    This is a known pain point in Spiff/ICM the tool is calculating off a live field (

    Close Date) instead of a locked, point-in-time snapshot. The fix isn't really "how do I stop deals from being backdated" it's "stop letting a mutable CRM field drive an immutable financial record." 

    Root cause: Spiff's plan logic is likely referencing Opportunity.CloseDate (or a similarly live-synced field) to bucket the deal into a payout period. When that field changes after calculation/payout, any report or re-run that re-evaluates the deal picks up the new value, creating a mismatch between "period paid" and "period the deal now says it belongs to." 

    How to actually fix it a few layered options, roughly in order of how I'd sequence them: 

    1. Snapshot the period at calculation time, don't derive it live. Add a dedicated field something like Commission_Period__c on the commission/statement record (or in Spiff's own statement object) that's set once when the statement runs and never recalculated from CloseDate again. Spiff does support adding effective dates on plans/logic and locking historical statements, so this should be a config change in Spiff's plan design rather than custom Apex — check that "lock historical statements" setting is actually turned on for closed periods.
    2. Separate "Close Date" (sales-facing, editable) from "Commission Effective Date" (finance-facing, locked once a statement is generated). Reps and deal desk need to edit Close Date for pipeline/forecast reasons that's normal. The commission engine should never read that same field for historical periods once paid.
    3. Treat post-payout edits as a reconciliation event, not a silent recalculation. If a close date changes after a statement already paid against it, that should trigger a clawback/adjustment workflow (a new adjustment line in the next period), not a retroactive rewrite of March's numbers. This is standard ASC 606-adjacent practice Spiff's audit-ready expense reporting is built around exactly this kind of compliant, locked-period model.
    4. On the Salesforce side, if Opportunity edits are what's causing this, consider a validation rule or Flow that blocks/flags Close Date changes on Opportunities that already have a Commission_Statement__c (or equivalent) linked and Closed/Locked at minimum, notify Finance/RevOps rather than letting it happen silently.

    I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Escribir una respuesta...
0/9000
Aadhar Agarwal preguntó en #Revenue Cloud
19 ago, 04:47
Headless Product Configurator Business APIs (load-instance/add-nodes/save-instance) return 403 FUNCTIONALITY_NOT_ENABLED: [IHeadlessConfiguratorFamily] in Developer Edition

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 *

3 respuestas
  1. Aadhar Agarwal (Mirketa)
    2 sept, 03:56

    Hi @Christopher Strecker

    , That's the missing piece. By assigning "Product Configurator API User" permission to my user, I was able to connect without any error. 

    Hi , That's the missing piece. By assigning

     

     

Escribir una respuesta...
0/9000
Eric Dreshfield (Principal Consultant en Dresh For Success LLC)
3 ago 2019, 13:36

Cash flow is the amount of cash a company has, or expects to have, on hand at any given time. Are you struggling to manage your cash flow? You need a revenue management system. Read this blog to learn the 5 key benefits of an effective revenue management system.

The 5 Key Benefits of an Effective Revenue Management System

2 comentarios
Escribir un comentario...
0/9000