What is the correct order of data import to load Products and Product bundles in CPQ?
In Salesforce CPQ, importing data for products and bundles requires a specific order to ensure referential integrity, as certain objects depend on others being present. The correct sequence starts with the Product (the parent record), followed by Product Features (defining sections or categories within the bundle), Product Options (specific selectable items under features), Option Constraints (rules governing option selections), and finally Configuration Attributes (additional settings for dynamic configuration). Option A reflects this hierarchical dependency accurately. Option B includes unrelated objects like Product Action and Error Conditions, which pertain to rules rather than bundle structure. Option C starts with Product Option before Product, which violates dependency rules since options require a parent product. Option D begins with Product Features before Product, which is incorrect as features need a product to associate with. Salesforce CPQ documentation emphasizes this order for successful data imports.
An Admin wants to generate one Asset record for each Quantity of a new Product. Currently, zero Asset records are generated for this Product when included on Quotes that are Contracted.
Which setting should the Admin change to meet the business requirement?
Requirement Overview:
Admin needs to generate one Asset record for each unit of the Product upon contracting.
Solution Details:
The Asset Conversion field determines how Salesforce CPQ creates Asset records from Quote Lines.
Setting Asset Conversion to One per Unit ensures that for each quantity of the Product, a corresponding Asset is created.
Steps to Configure:
Navigate to the Product record.
Locate the Asset Conversion picklist and select One per Unit.
Save and test the configuration by creating a Quote, contracting it, and verifying the Asset creation.
Cloud Kicks (CK) uses Salesforce CPQ to streamline its sales process for customers, partners, and distnbutors. As part of CK's implementation, sales reps are able to specify a Partner Discount within the Quote Line Editor.
Sales reps are reporting the Quote and Quote Lines' prices fail to recalculate automatically after a value is entered or changed m the Partner Discount field. The reps must press the Save or Quick Save button manually to trigger the calculation instead. How can the consultant ensure the real-time calculation is triggered in response to field changes within the Quote Une Editor?
Real-Time Calculation:
The Calculate Immediately field in CPQ ensures that pricing calculations occur automatically when changes are made in the Quote Line Editor without requiring manual saving.
Field Behavior:
Enabling this field configures CPQ to detect changes to the Partner Discount or other relevant fields and trigger real-time recalculations.
Salesforce CPQ Reference:
Configuration settings for real-time pricing calculations are documented in the Pricing and Calculation Package Settings .
Universal Containers (UC) sells to partners in multiple regions. Each region has a unique price multiplier that should be applied to the pricebook price of the product.
A custom object has been created to maintain the regional multipliers for each region. Any discounts should be applied after the regional multiplier has been applied. An admin needs to create a Lookup Price Rule.
Which field should the admin configure the price action to update?
Scenario:
Apply a regional multiplier to the pricebook price and subsequently apply discounts.
Solution:
The Customer Price field stores the post-regional multiplier price, enabling further discounting.
Why Other Options Are Incorrect:
A: Special Price is used for manual overrides, not automated calculations.
B: Partner Price is unrelated to the customer's pricing structure.
D: List Price remains constant and does not reflect discounts or multipliers.
Salesforce CPQ Reference:
Price Rules and field updates are detailed in CPQ Pricing Logic Guidelines .
Northern Trail Outfitters (NTO) has a growing list of Products. NTO has experienced challenges in keeping its bundled Products up-to-date and has asked the CPQ Specialist if there is a better way to manage its Product catalog.
Which option is the most appropriate for the CPQ Specialist to suggest first?
Dynamic Features:
A Dynamic Feature allows administrators to automatically update or populate Product Options for a bundle based on defined rules and conditions.
Filter Product Rules:
Applying a Filter Product Rule ensures that only relevant or newly available products appear as options for the bundle. This reduces manual maintenance while keeping the bundle dynamic.
Salesforce CPQ Reference:
Dynamic Features and Filter Product Rules are part of advanced bundling techniques documented under Product Configuration .
Bundle Configurations Wilson
12 days agoRonald Clark
1 month agoKaren Cooper
26 days agoBetty Thomas
17 days agoLinda Young
13 days agoMichelle Roberts
1 month agoAshley Adams
10 days agoHeike
2 months agoVeronique
2 months agoChandra
2 months agoShad
2 months agoViki
3 months agoIn
3 months agoAnglea
3 months agoHui
3 months agoCarlee
4 months agoJustine
4 months agoDeeann
4 months agoKenia
4 months agoVernell
5 months agoSalena
5 months agoMa
5 months agoDonette
5 months agoMarshall
6 months agoHenriette
6 months agoEugene
6 months agoFelix
6 months agoKeshia
7 months agoRenea
7 months agoKeneth
7 months agoKristin
7 months agoReena
8 months agoWinfred
8 months agoLuke
8 months agoVeronique
8 months agoLai
8 months ago