Skip to main content

#Revenue Cloud87 人正在讨论

Hi everyone,

I’m facing an issue in Salesforce RLM where I need to apply a manual amount discount at the bundle level. The package price is $0, and each bundle has a different discount amount.

 

I tried using DDS (Discount Distribution Service) and Header Adjustments. After adding the discount, I’m getting the following error:

“We couldn't refresh the prices and validate the configuration. Ask your Salesforce admin for help. We couldn't fetch the data for ExtSalesTransactionContext context definition. Try again later or contact your Salesforce admin for help.”

 

Also, when I try to enter a discount amount for a package with a Sales Price of $0, I get this validation error:

“Specify a number that's between 0 and Sales Price amount: Discount (Amount)”

 

Is there a way to disable or modify this validation so that I can apply a discount amount when the Sales Price is $0?

 

I referred to the Salesforce documentation for Header Adjustments.

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

 

Any guidance would be greatly appreciated.

Thank you!  @Jayaprakash . @Kaamil Siddiqui  #Revenue Cloud @* Salesforce Revenue Cloud *

0/9000

Can you renew a Contract or only Assets?   

If you can renew a Contract, please share any setup pre-requisites and execution steps. 

 

If Contracts cannot be renewed, what other options do you have for the Contract End?  What happens to Assets under a Contract beyond the Contract End Date? 

 

Thank you!

2 个回答
  1. 今天,11:55

    Thanks Yogaraj, but what about Contracts, can you renew a Contract like you can an Asset?

0/9000

Hi Everyone,

I’m not able to see the product under the category when I try to add it to a Quote through Browse Catalogs, even though the product is active and assigned to an active Pricebook that is aligned with the Quote’s Pricebook.

Could someone please help me check if I’m missing any configuration or setup?

Thanks in advance! 

 

#Salesforce  #Revenue Cloud  #Salesforce Revenue Cloud

1 个回答
0/9000
0/9000

We're on Agentforce Revenue Management (ARM). We have a requirement to periodically check whether a Renewal Quote (auto-generated ahead of a contract's end date) still matches the current state of the customer's Assets — since amendments or cancellations can happen after the renewal quote is created but before it's finalized. Our objective is to refresh the renewal quote for any changes in the Contract after the renewal quote is created.

 

We're trying to understand the correct data model traversal for this in ARM, given the objects involved: 

  • Contract — the source contract being renewed
  • Asset — related to the Contract
  • AssetContractRelationship — junction object between Asset and Contract
  • AssetAction — the transaction log capturing lifecycle events (amend, renew, cancel) on an Asset

 

Questions for the community: 

  1. What is the standard/recommended relationship path from a Quote (or Contract) to determine which Assets are currently associated with it — direct Asset.ContractId, or through AssetContractRelationship? When does ARM use one versus the other?
  2. Is AssetAction intended to be queried directly to detect "has this Asset changed since a given date," or is that considered an anti-pattern (i.e., should current state be read only from Asset's own fields, with AssetAction treated purely as historical/audit data)?
  3. Is there a standard/OOTB field or relationship that ties a Quote or its Quote Line Items back to the Asset(s) it's renewing, or is Contract the only reliable join point?
  4. Are there known data model diagrams or official Salesforce documentation that cover this specific Quote/Contract/Asset/AssetContractRelationship/AssetAction relationship set for ARM specifically (as opposed to CPQ Classic)?

Any pointers to official documentation, Trailhead modules, or real implementation experience would be appreciated.

1 个回答
  1. 今天,02:21

    I am not sure, you can rely on AssetContractRelationship, my understanding was, this object being used after the Order assetized.  

    In your case, you need to rely on the Renewal QuoteLineItem.QuoteAction field and its SourceAsset field to traverse back to the original asset. 

0/9000

We are using Agentforce Revenue Management (RCA). Our client uses Quote Line Groups with ramped segmentation. When we contract the quote, we get assets with asset state periods for each segment.

 

When we create a renewal quote using Renew Asset Action for a contract, renewal quote gets created without any groups and segments. Although the original asset has three segments, renewal quote creates lines without original groups and segments. It creates only quote line for only one year although the original contract was for three years. 

 

If there is no out of the box solution, how can this be accomplished?

 

Is there any out of the box solution to create renewal quote with the original contract term and segments with future renewal dates.

1 个回答
0/9000

Does anyone know if to disqualify a product, we strictly need to create a Product disqualification record?

The use case I have is that we want to replace entitlement policies with disqualification rules, and basically we have a custom field on the product2 object, we want to disqualify (and hide in our storefront) all products that don’t have an specific value on that picklist field (value != goodValue). 

All examples I could find involved creating records for the disqualification standard object, and I want to know if that is the only way. Category disqualification is not applicable as we still want to see those specific categories on the storefront, only products hidden.

If there is no way to do that then I would need to create a disqualification record for each product I want to disqualify, which would be a lot of tech debt.    @* Salesforce Revenue Cloud * 

3 个回答
  1. 今天,01:40

    Yes, you need to create as much as record for those disqualification. Its applicable to individual products, If those products are not allowed to sell, consider moving those products into different category, so that, you have to create only one Product Category disqualification and build a process around when it become eligible.

0/9000
1 个回答
  1. 8月16日 14:44

    Hi Lohith - that error is purely about the Rate field's size, not the value being 'wrong'. The field is defined to hold 3 digits before the decimal and 2 after (so its max is 999.99), and 1800.0 needs 4 digits before the decimal, which overflows it. 

     

    Two ways to fix it, depending on the field: 

     

    1. If 'Rate' is a custom field you or your team created: go to Setup > Object Manager > [the object] > Fields & Relationships > Rate > Edit, and increase Length (the digits to the left of the decimal) to at least 4, keeping Decimal Places at 2. That lets it store 1800.00. Save and re-enter the value. 

     

    2. If 'Rate' is a standard/managed Revenue Cloud field (the Edit option is greyed out and you can't change its length): the cap is intentional, and it usually means the field expects a different kind of value than you're entering - most 'Rate' fields in pricing are a percentage, not an amount. So a value like 1800 may belong in a different field (an amount/price field), or needs to be expressed differently. Check the field's type and help text to confirm what it's meant to hold. 

     

    Quickest way to tell which case you're in: open the field in Object Manager. If it's editable, resize it (option 1); if it's managed/locked, it's option 2 and you'll want the right field for that value. 

     

    Hope that clears the error!

0/9000

When a Renewal Quote is created from a Ramp Contract, the expected Ramp Segments are not being created on the Renewal Quote. 

Is this the standard Salesforce behavior

for Ramp Renewals? If not, what configuration or process is required to automatically create the Ramp Segments on the Renewal Quote based on the original Ramp Contract?  

 

#Revenue Cloud  #Salesforce Revenue Cloud  #Salesforce Developer

0/9000

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 * 

1 个回答
0/9000