Requirement Overview:
A product priced at 100 USD and 95 EUR needs to be included as part of a bundle.
Solution:
Bundled Products: Setting the Bundled field to True ensures the product is included in the bundle's total price.
Configure the Price Book Entries with the required prices for the respective currencies.
Steps to Configure:
Navigate to the Product in the 2019 Price Book.
Set 100 USD and 95 EUR as the Price Book Entries.
On the Product Option, mark the Bundled field as True.
Validation:
Test the bundle by adding it to a Quote and verifying the correct pricing behavior.

Issue Context:
Some Opportunity Products are not syncing from the Quote, causing pipeline inaccuracies.
Troubleshooting Steps:
A). Ensure the Quote's Account lookup is populated:
A missing Account lookup can prevent synchronization as it ties the Quote to the Opportunity.
B). Ensure the Opportunity's Primary Quote lookup is populated:
The Primary Quote must be explicitly linked to the Opportunity for synchronization to occur.
E). Check the Quote's Primary checkbox for a value of True:
Only the Primary Quote syncs Opportunity Products. Ensure the checkbox is set to True.
Validation:
Verify that Opportunity Products sync correctly after ensuring these fields are properly populated.

* Understanding the Requirement:
* Universal Containers wants sales reps to associate Campaign records with Quote Lines using a lookup field in the Quote Line Editor.
* The requirement includes avoiding warning messages when searching for Campaign records.
* Salesforce CPQ Lookup Field Behavior:
* When a lookup field is added to the Quote Line Editor, Salesforce CPQ searches for records in the target object (e.g., Campaign).
* To avoid warnings, the target object (Campaign) must have a specific field set named CPQ_Lookup, which defines the fields displayed in the search results.
* Steps to Implement the Solution:
* Step 1: Navigate to the Campaign object in Salesforce Setup.
* Step 2: Go to the "Field Sets" related list and click "New."
* Step 3: Name the field set CPQ_Lookup (case-sensitive).
* Step 4: Add the fields you want to display in the lookup search results (e.g., Campaign Name, Start Date, Owner).
* Step 5: Save the field set.
* Integration with the Quote Line Editor:
* The system will now use the fields defined in the CPQ_Lookup field set when sales reps perform a search for Campaign records.
* This ensures the lookup field operates without errors or warnings in the Quote Line Editor.
* Key Considerations:
* Ensure that all required fields for identifying Campaign records are included in the CPQ_Lookup field set.
* Test the lookup functionality in the Quote Line Editor to confirm smooth operation.
* Validation:
* Add a Campaign lookup field to a Quote Line in the Quote Line Editor and test the search functionality. Verify that the fields defined in the CPQ_Lookup field set appear in the search results without warnings.
References:
Salesforce CPQ documentation on setting up lookup fields and field sets emphasizes creating a CPQ_Lookup field set to avoid warnings

Requirement Overview:
Universal Containers wants to update the Quantity of a specific Product in the Quote Line Editor via a Price Rule.
The Price Rule should target only this specific Product.
Key Mechanism:
Use a Price Condition on the Price Rule to evaluate a Quote Line field that uniquely identifies the Product (e.g., Product Code or Product Name).
Steps to Configure:
Navigate to the Price Rule.
Add a Price Condition:
Field: Select a field from the Quote Line that identifies the Product.
Operator: Equals.
Value: Enter the unique value (e.g., Product Code or Name). Configure the Price Action to update the Quantity field.
Validation:
Test the rule by adding the specific Product to a Quote and confirming that the rule updates its Quantity as expected.

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.
References: Salesforce CPQ Documentation - "Importing Product Data" and "Bundle Configuration Setup".