Salesforce Certified CPQ Specialist — Question 24

The Admin at Universal Containers recently created a new custom field referenced on the Target Field on a Price Action in a Price Rule. While testing the Price Rule, the Admin noticed that the Price Action failed to populate the custom field. The Admin checked the CPQ Package Setting and noticed that the Triggers Disabled checkbox was checked. After unchecking Triggers Disabled, the custom field still failed to populate.
How can the Admin ensure this custom field can be referenced by the Calculator?

Answer options

• A. Revoke the Advanced Calculator and re-authorize the Calculation Service.
• B. Re-execute the Post Install Script in Package Settings to ensure the Calculator Referenced Fields are up-to-date.
• C. Rename the custom field label, then recreate the Price Action to reference the new field label.
• D. The Admin must reference a standard CPQ field because custom fields are unsupported with Price Rules.

Correct answer: B

Explanation

The correct answer is B because re-executing the Post Install Script ensures that all Calculator Referenced Fields are current, which can resolve issues with custom fields not populating. Option A is incorrect as revoking the Advanced Calculator does not directly address the field population issue. Option C does not solve the underlying problem of the custom field not being recognized. Option D is also incorrect because custom fields can be used in Price Rules, provided they are properly configured.