#CPQ13 debatiendo

Customer success is at the heart of everything we do at Kugamon. 

We’re grateful to Christian Gennerman for sharing his experience with Kugamon and highlighting what matters most to us — delivering exceptional support alongside powerful Quote-to-Cash solutions. 

“Kugamon works exactly how we need it. The real bonus is the customer service.” 

Christian shared how our team provides responsive support, meaningful answers, and a willingness to connect directly when help is needed. 

We believe great technology is only part of the solution — having a dedicated team that understands your goals and is there when you need us makes the difference. 

Thank you, Christian, for trusting Kugamon and sharing your experience with our community! 

Hi Everyone, 

while doing the trailhead challenge i'm facing the error. i've attached the reference image below. Could anyone please help 

There was an unhandled exception. Please reference ID: XRSJHNFB.

#Trailhead Challenges #CPQ

Hello, 

Currently our system is built that upon the creation of a quote for a new sale they set a custom Contract Term field on the quote to the length they want the term to be (for example, 36) and then on the quote they set the Subscription Term to 12. They have automation that then creates a Master Agreement that is a high level agreement that contains the full length of the contract (for example, start date of 1/1/2026 through end date 12/31/2029) and on the master agreement the contract term says 36. And then there is a child agreement that is related to the master agreement (a child to this agreement) that has a contract term of 12 and a start date of 1/1/2026 through 12/31/2026. Then on 12/30/20206 they create a new Subscription Agreement via an auto renewal process for Year 2 with dates of 1/1/2027 through 12/31/2027. Then do the same thing at Year 3 for dates of 1/1/2028 through 12/31/2028. Then on 1/1/2029 they complete what is called a contract renewal where the above starts over again with a new master agreement then child subscription agreements. 

Now with a new sales they want to move to a quote with the custom contract term of 36 months and subscription term of 36 months but within the quote are quote line groups for Year 1, Year 2, Year 3 of 12 months. When the contract creates they want one contract containing the whole contracts information. Then at the end of the 3 years the "contract renewal" occurs for the 36 months for the contract term and Subscription Term. 

The issue is existing contracts on the old structure. How do we handle the interim subscription agreements before the contract renewal if we remove the master agreement. And then how do we move to the new contract renewal process at the end of the compete term. I am assuming some sort of data migration but not sure what that would be or would look like. 

Has anyone else had to go through this? And nope they do not want MDQ. 

Thank you. 

🚨 HIRING | SALESFORCE CPQ DEVELOPER 🚨

🚀 Looking for a Salesforce CPQ Developer to join a Leading Global Consulting & Professional Services Organization.

📍 Hyderabad | Gurgaon

🏠

💼

4+ Years 

⚡

🔥 Key Requirements

✅ Strong Salesforce & Salesforce CPQ

experience 

✅ Hands-on

experience 

✅ Experience delivering end-to-end CPQ projects 

✅ Strong CPQ configuration & development skills

🌟 Exciting opportunity to work on impactful Salesforce CPQ projects with a global organization!

📩 Share your CV: supriyah@wen-jobs.co.in

📞

7892999581 

PLEASE ANSWER ONLY IF YOU ACTUALLY KNOW 

WHAT YOU ARE TALKING ABOUT.  ChatGPT and Google did not help. DO NOT PASTE THAT JUNK HERE. Get Answer Leaderboard "points" on someone else's time. 

I have the System Admin profile with View All Data and Modify All Data permission.  I cannot see the New Quote button in the header on Opportunity Lightning Pages.  I have a user with a Business profile who also cannot see the button.  I have a different user with a Sales profile who CAN see the button.  In my Sandbox, I switched the blocked user to the Sales profile, logged in as him, and still cannot see the button.  When I log in as the Sales user I can see the button.  I checked different record types in different apps.  The Sales user always sees the button the Business user and Sys Admin never see the button. 

All three profiles see the same page layout for each Opportunity Record type.  "New Quote" is a custom create record action on the Opportunity object.  It works for the Sales user with no issues or errors.   

"New Quote" is an Action on the Opportunity object.  It is not a Global Action.  I checked the fields on the Action Layout and the predefined fields in the Action.  All three profiles have View permissions on all fields and none of the fields are Read Only for anyone.  The Object of the Action is Opportunity and the target is Quote.  The Record Type is Master.  The Sales and Business profiles have Master as the default Record Type for Quotes.  Sys Admin has Standard as the default Record Type.

All three users are Flow users.  All three users are Marketing users.  We all have the Salesforce CPQ User (or Admin) permission set.  We all have the CPQ permission set license.  We all have the CRM permission set license. 

The Lightning Page we are seeing i the org default.  When I view the page in the Lightning Editor, I still don't see the "New Quote" button in the header.  There is no filter on the header component.  The same Compact Layout is assigned to all Record Types. 

The only CPQ plug in we have is a Product search.   We do not put Quotes in Queues.  We do not use Roles and Hierarchy.

What am I missing? 

#CPQ  #CPQGurus  #Quotes  #Opportunities  #Pagelayouts  #Lightning App Builder  #User Profiles  #Quick Actions

We have a product rule set up as follows in Sandbox and Production. Below is the Current Product Rule Configuration.  

Product Rule Header: 

• Type=Selection 
• Conditions Met = All 
• Scope = Product 
• Evaluation Event = Always 
• Evaluation Order = 10 

Error Condition: 

• Tested Object = Quote 
• Tested Field = Boost = True
• Operator = equals 
• Filter Type = Value
•  Filter Value = TRUE 

Price Action 1: 

• Product = Product A 
• Type = Enable 

Price Action 2: 

• Product = Product B 
• Type: Enable & Add 

Price Action 3: 

• Product = Product C 
• Type = Enable & Add 
• Required = True 

Price Action 4: 

• Product = Product C 
• Type = Hide 

Configuration Rule

:  

Product = Bundle 1  

Results in the Configurator

In Sandbox the following is occurring in the Configurator:

• Product A is not appearing
• Product B is not appearing
• Product C is appearing and checked

In Production the following is occurring in the Configurator:

• Product A is appearing
• Product B is appearing and checked
• Product C is not appearing

What the Sales team would like to have happen is:

• Product A is appearing
• Product B is appearing and checked
• Product C is appearing and checked

What correction needs to happen to get this to occur? At a minimum I would think I would delete Product Action 4. 

Thank you. 

Rachel 

#Salesforce CPQ & Billing  #CPQ @* Salesforce Revenue Cloud *

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 *

I have two items related to reconfiguring bundles and how to handle existing subscriptions and assets. 

Currently we have a bundle configured as below:

1. Bundle Header (Parent) - Product A (renewable subscription that has a price associated with it)
   1. Child Product (product option) - Product B (one-time asset that has a price associated with it).

When added to a quote, since the child is not flagged as Bundled, pricing sits at both lines. The business now wants to re-design the bundle. They want it to look like the following:

1.  Bundle Header (Parent) - Product C (renewable subscription that has a $0 price)
   1. Child Product (product option) - Product A (renewable subscription that has a price associated with it).
   2. Child Product (product option) - Product B (one-time asset that has a price associated with it).

Pricing would sit at each child product line. I was thinking I could just reconfigure the bundle by creating the bundle header and adding Product A as a child and then Product B as a child. And remove the child option (product B) from from Product A (basically breaking the original bundle apart).  

But my concern is existing data that was sold under the current configuration. Do I create subscription bundle headers and then realign the current subscriptions and assets to the new bundle header (adding the Root ID, Required By ID, adjust the product option information on each subscription and asset)? If so, what are the possible risks to amendments and renewals? If this is not the best approach what would you suggest? I can’t create new product codes so I need to use the current products and product codes. 

We have a one time subscription Service product that is part of two bundles. We want to break this apart from the bundles to make it standalone and have it only added on new sales quotes. This Service product is a one-time subscription product.  

For new sales, I need to hide the options within the two bundles and have the product auto added. For amendments, I need the options available for the products being revised but if we are adding one of the two bundles for the first time we need the option for the Service product hidden in both bundles.  

How would i build this? For new sales I am thinking a product selection rule to add the standalone product. For new sales a product selection rule to hide the options. For amendments, how would I approach this? 

Thank you.