#Salesforce Revenue Cloud39 debatiendo

Hi everyone,

I am facing an issue with a Group Ramp Deal in Salesforce Revenue Cloud and would appreciate your guidance.

Scenario:

1. I created a 3-year Group Ramp Deal with the Ramp Uplift Type set to Compounding Uplift/Standard Uplift.
2. The uplift percentages are configured as follows:
   • Year 1: 0%
   • Year 2: 10%
   • Year 3: 10%
3. I successfully created the order and the corresponding asset.
4. When I renewed the asset using Override Renewal Term and configured the renewal as the same Group Ramp Deal, I noticed that the Net Unit Price is not populated for the first year, whereas the pricing is calculated correctly for the second and third years.

Has anyone encountered a similar issue when renewing a Group Ramp Deal with Compounding Uplift in Salesforce Revenue Cloud? Are there any specific configurations or additional steps required to ensure that the first-year pricing is calculated correctly during renewal?

Any suggestions or insights would be greatly appreciated.

Thank you! 

Hello Trailblazer Community! 👋

I have 10+ years of experience in Software QA, ETL Testing, Data Quality, SQL, Test Automation, Functional Testing, and UAT.

I am transitioning into the Salesforce ecosystem with the goal of becoming a Salesforce Functional Consultant, focusing on Sales Cloud, Salesforce CPQ, Revenue Cloud, and Agentforce.

I am currently building hands-on Salesforce portfolio projects to strengthen my understanding of business requirements analysis, business process mapping, user stories and acceptance criteria, product configuration and pricing, Quote-to-Cash processes, functional testing, and UAT.

I am particularly interested in understanding how Salesforce solutions are designed and implemented to solve real-world business problems.

I would love to connect with Salesforce Functional Consultants, Business Analysts, CPQ and Revenue Cloud professionals, Agentforce specialists, and Salesforce implementation partners.

I welcome opportunities to learn from experienced professionals, exchange knowledge, build meaningful connections, and explore relevant career opportunities in India.

If you have any advice for someone transitioning into Salesforce Functional Consulting, I would be grateful to hear your suggestions.

Looking forward to connecting with fellow Trailblazers!

Thank you!

#Sales Cloud  #Salesforce Revenue Cloud  #Salesforce CPQ & Billing  #Agentforce  #Salesforce Admin

We are migrating from Salesforce CPQ to Revenue Cloud (Agentforce Revenue Management), API v67/v68. We have a custom picklist field Action_Type__c (Add, Amend, Cancel, Renew, No Change, Transfer, Cancel and Renew) that we stamp on Quote Line Item and Quote Action, and it flows to Order Product through the Sales Transaction context definition (Sales Transaction Item attribute mapped in QuoteEntitiesMapping and OrderEntitiesMapping). That part works.

We want the same value on Asset Action and Asset Action Source after the order is activated and assets are created or updated (createOrUpdateAssetFromOrder, called from a record-triggered flow on Order).

What we tried:

1. Created Action_Type__c (picklist) on Asset Action and Asset Action Source.
2. In the context definition: added a custom attribute on the Asset Action Source and Asset Action nodes, hydration mapping in AssetEntitiesMapping (Asset Action Source to Asset Action Source), and in AssetToSalesTransactionMapping the Asset Action Source to Sales Transaction Item mapping with ctxAttrHydrationCtxs, following the same pattern we use for another custom field (Average Unit Price).
3. Activated new versions and ran fresh amendment and renewal orders.

Result: Order Product has the value, but Asset Action and Asset Action Source stay blank. Asset Action and Asset Action Source are not createable or updateable through the API or Apex, so we cannot backfill them either. The only link we have is AssetActionSource.ReferenceEntityItemId (polymorphic to OrderItem or OrderItemDetail).

Questions:

1. Is it supported to persist a custom field value onto Asset Action or Asset Action Source when assets are created from orders? If yes, which context mapping, node or setting is required (is the Asset context mapping used on the write path, or only for hydration)?
2. Does createOrUpdateAssetFromOrder copy any custom fields from Order Product to Asset Action Source, and if so how is the mapping defined?
3. If it is not supported, what is the recommended pattern for reporting the originating action type per Asset Action (sidecar object populated by an Apex trigger on Asset Action Source, or something else)?

Any pointers to documentation or a release note would be appreciated. 

Hi all, 

I'm exploring Product Catalog Management in Revenue Cloud and trying to understand the practical purpose of Product Specification Types and Product Specification Record Types. 

my understanding is A Product Specification Type lets you define industry-specific product lines. 

and Product Specification Record Type links that type to a Record Type on Product2 and sets whether the product is commercial (sellable) or non-commercial. 

- Both are optional and are deployed as metadata.  

 I can see Commercial and Technical record types OOB. Has anyone customised this in a project?  

Any examples, lessons learned or pointers would be much appreciated.  

doc: 

https://help.salesforce.com/s/articleView?id=ind.product_catalog_product_specification.htm&type=5

#Revenue Cloud    

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. 

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