#Revenue Cloud84 debatiendo

Hello, 

I am trying to complete this

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. 

Anyone else running into recalculation headaches with Spiff/ICM when a deal gets reassigned to a different rep mid-period? Mine ends up double-counting or dropping the payout entirely, curious how others are handling ownership changes without breaking the calc.  

Renewal Opportunity Creation  Scenario: 30 days before a Contract expires, automatically create a Renewal Opportunity and notify the Account Owner.  Questions:  • Which Flow type would you use?   • How would you calculate the 30-day window?   • How would you prevent duplicate renewals?     

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). 

We're planning a large migration of legacy Asset records into Revenue Cloud and want to confirm we're not missing a bulk-friendly path. 

We've confirmed HasLifecycleManagement, LifecycleStartDate/EndDate, and the underlying AssetStatePeriod object are all read-only via standard DML - Data Loader/Bulk API reject any attempt to write them (INVALID_FIELD_FOR_INSERT_UPDATE). 

The only supported path we've found is the Connect REST API generate endpoint (asset-management/assets/actions/generate). It looks like a single-asset-per-call API with no bulk/batch equivalent, and the start date of the first asset state period is locked once the call completes. 

Has anyone done a large historical Asset migration into lifecycle management this way? Curious about: 

- Whether a bulk-friendly path exists that we're missing 

- Realistic call volumes/patterns others have used against the generate endpoint 

- Whether it's common practice to leave older/inactive assets non-lifecycle-managed and only onboard active ones 

1. Appreciate any recommendations.

#Revenue Cloud

Hi everyone, 

I'm currently working on attribute-based pricing in Salesforce Revenue Cloud and came across a scenario I'd like some guidance on. 

For example, I have an attribute called Color. If Color = Blue, I want to apply a 5% discount. This pricing rule should apply to every product in my product catalog. 

Using Price Adjustment Schedules , the pricing adjustment is tied to a specific product. This works well for a small catalog, but in a large product catalog with thousands of products, creating and maintaining separate Price Adjustment Schedules for each product is time-consuming and difficult to manage. 

Is there a way to define the pricing logic once and have it apply to all products instead of configuring it product by product? 

I'd appreciate any suggestions or best practices. Thanks!   

@* Salesforce Revenue Cloud * 

We have one Bundle Product

 with 10–15 unique child products (for example: iPhone 15, iPhone 16, Samsung, etc.). 

We want to use 

Attributes instead of Product Related Components and Product Component Groups

. 

Requirement:

•  Create attributes for each product option. 
•  If the bundle has 15 child products, create 15 attributes. 
•  All attribute options should be available for selection. 
•  When the user selects the required attribute value, the corresponding child product should automatically be added with its respective pricing. 
•  When the user selects any Bundle Product, all related attributes should be automatically added. 

Question:

Can we achieve this functionality using Attributes only, where all child products are mapped through attributes and selected products are automatically added with the correct pricing, without using Product Related Components and Product Component Groups? 

The issue is right now when I renew a term based bundle which consists of One time child component as well, it shows me the one time product too with 0 quantity, I don't want that I want to skip the one time products completely inside a bundle. How can I achieve this? 

Approach used: The amend, renew and cancel flow is passing the assetIds but it is passing of bundle only.    

what should be the data type of the attribute in context definition in RCA  if data type of quote field is currency and data type of order field is double ?