How can the Admin ensure this custom field can be referenced by the calculator?

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?
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.

Answer: D