SALES-ADMN-202 practice question 7 of 30

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…

Full set: 213 questions
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: The Admin must reference a standard CPQ field because custom fields are unsupported with Price Rules.
B: Revoke the Advanced Calculator and re-authorize the Calculation Service.
C: Rename the custom field label, then recreate the Price Action to reference the new field label.
D: Re-execute the Post Install Script in Package settings to ensure the Calculator Referenced Fields are up-to-date. Correct answer
Correct Answer:
D. Re-execute the Post Install Script in Package settings to ensure the Calculator Referenced Fields are up-to-date.
Explanation

The Salesforce CPQ Advanced Calculator service needs to be explicitly aware of any custom fields it must read from or write to. This is managed through special field sets, primarily the 'Calculating Fields' field set on objects like Quote Line. When a new custom field is created, it must be added to this field set. The Post Install Script, when executed from the CPQ package settings, helps ensure that all package configurations, including field sets and other dependencies, are correctly registered and up-to-date. This action can resolve issues where the calculator is not recognizing a newly added field.

Why Incorrect

A. Custom fields are fully supported in Price Rules and are a common part of CPQ configurations. This statement is factually incorrect.
B. Re-authorizing the Calculation Service is a troubleshooting step for authentication or connectivity issues, not for making the service aware of new metadata like a custom field.
C. Field labels are for the user interface; the calculator references the field's API name. Renaming the label would have no effect on this issue.

References

1. Salesforce Help. (2023). CPQ Package Settings. Salesforce CPQ Documentation. Section: Additional Settings. "Execute Scripts: Runs post-installation scripts that you would otherwise have to run after a package upgrade. The scripts ensure that all your package-level settings are configured correctly."

2. Salesforce Help. (2023). Special Fields. Salesforce CPQ Documentation. "To use your custom field in a price rule, add your field’s API name to the Calculating Fields field set on your quote line object."

Scroll to Top