* Salesforce Revenue Cloud *

I’m having trouble with a Revenue Cloud instance. Every time I try to add a bundle to a quote, I get the following error:

“Verify if fields like Component, Virtual Component, or backend configuration block it from being quoted outside of its parent bundle.”

The system works normally when I try to add a standalone product. The issue only occurs with the bundle, and I’m not trying to perform an amendment—just add a new product.

Is anyone else encountering this same error?

Hi everyone, Is there a way to populate the Quote field "Region__c" from the Account field "Region__c" using Context Definition only? 

I'm curious if this is achievable purely through Context Definition (without Flow or Apex) — has anyone done this before? Please help. 

Thanks! 

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 * 

Specifically, how are you managing dunning, payment reminders, and collections follow-up? Built in-house with Flow, a third-party AR tool, or still mostly manual/spreadsheet-based?  

Disclosure: I work on Quick Receivable, a Salesforce-native AR automation app. I'm trying to understand what's actually working for teams before assuming we have the answer

I have created a product category disqualification.  But, under quote when I click "Browse Catalogs" that particular category is visible.  I have even refreshed decision tables(Product Qualification, Product Disqualification) but still it isn't working.  Can anyone help me?     @* Salesforce Revenue Cloud * 

Anyone else dealing with the CPQ → Revenue Cloud switch?

CPQ is in end of sale now, and I've been reading up on how people are actually handling the move instead of just panicking about the deadline. Biggest thing I noticed: nobody does a straight cutover. Everyone phases it in, mostly because CPQ configs tend to have years of pricing logic nobody remembers setting up.

Found a solid writeup on the whole process if anyone wants it.

Would love to hear how it's actually gone for people, good or bad.