Explanation:

The issue is that the error message appears too early (before clicking Save). Here’s why option D fixes it:

1. Product Rule Evaluation Event
By default, Product Rules can trigger validation errors immediately when conditions are met (e.g., during configuration).
Setting Evaluation Event = Save ensures the rule only runs when the user clicks Save, delaying the error until then.

2. Why Not Other Options?

A. "Evaluation Action = Save" → No such field exists in Product Rules.
B. "Apply Immediately = False" on Config Attribute → Affects attribute behavior, not rule timing.
C. "Apply Immediately = True" on Product Option → Would make the error appear even sooner (opposite of the goal).

Key Concept:
✔ Evaluation Event controls when a Product Rule executes (e.g., on Save vs. during configuration).
✔ For validation rules, Save is the correct event to avoid premature errors.

Explanation:

If some Quote products don’t sync to the Opportunity but no errors appear, it’s often due to:
a) Missing Price Book Entries for some products
b) Validation rules on the Opportunity Product silently stopping the sync
c) Products marked as "Exclude from Opportunity"
All these prevent products from being added without showing error messages.

Explanation:

Scenario Breakdown:

Issue occurs only when amending contracts and adjusting quantities of existing products.
Net pricing is incorrect (suggesting discounts are not applying correctly).

Why Option B is Correct?

Discount Schedules define tiered pricing (e.g., volume discounts).
If Cross Order is not enabled, discounts are calculated per order/contract.
During amendments, the system treats the adjusted quantity as a new order, ignoring prior quantities and resetting discounts.

Result: Incorrect net pricing because historical volume isn’t factored in.

Why Other Options Are Incorrect?

A. Revised Quantity is unrelated—it’s for tracking changes, not pricing.

C. Price Rule firing Before Calculate would affect all products (not just amended ones).

D. Price Rule firing On Calculate could impact pricing, but Effective Quantity changes would affect all scenarios (not just amendments).

Explanation:

Migration must follow dependency order:
1) Products (base records).
2) Options (added to bundles).
3) Attributes (used in rules).
4) Rules (rely on prior components).

Explanation:

Why Option B?

1. Filter Product Rule + Optional Filter Action allows UC to:

1. Default to eco-friendly products when the Opportunity is flagged.
2. Let sales reps override the filter to see all bundles when needed.
3. Maintain flexibility while guiding users toward preferred products.

2. How It Works:

The Filter Product Rule checks if the Opportunity is eco-friendly.

The Product Action applies an Optional Filter, meaning:
1. The filter is applied by default (showing only eco-friendly products).
2. Users can manually disable the filter to see all bundles.

Why Not the Other Options?

A (Search Filter with Hidden = FALSE):
Forces the filter to always apply without an override option.

C (Default field on Custom Action):
Doesn’t address filtering logic—just controls UI defaults.

D (Adding field to Search Filters Fieldset):
Makes the field searchable but doesn’t automate filtering based on Opportunity flag.

Implementation Steps:

1. Create a Filter Product Rule with a condition like:
Opportunity.Eco_Friendly_Flag__c = TRUE

2. Add a Product Action with:
Type = Optional Filter
Filter Logic = "Eco-Friendly OR IsBundle"

3. Assign to the Add Products action.