During interactive operations—such as quote creation or amendments—pricing calculations stop completely, throwing a hard Apex error:
Apex Error:
System.HandledException: Failed to reprice quote: UNKNOWN_EXCEPTION - An error occurred while executing CalculateDiscounts in CorePricingProcedure. MVEL list filter execution failed
When using legacy configurations or when a blank value slips into a downstream matrix mapping, the infrastructure logs a distinct pointer exception:
Execution Error:
An error occurred while executing LineItemFilter in CorePricingProcedure. Cannot invoke "Object.toString()" because the return value of "industries.context.api.service.model.runtime.query.TagData.getTagValue()" is null
To resolve these errors, update your pricing procedure design to place an explicit null guard at the absolute beginning of your filter criteria. This forces the engine to short-circuit the evaluation safely if data is missing.
In the App Launcher, find and select Expression Sets (or Pricing Procedures) and open the specific active version that is generating the error.
Locate the ListFilter or List Container element mentioned in your error logs or the step skipping your pricing logic.
Rearrange your logical statements so that the Is Not Null condition is evaluated first.
Incorrect (Crashes engine): LineItem.CustomFeeAttribute__c > 0 AND LineItem.CustomFeeAttribute__c Is Not Null
Correct (Stable execution): LineItem.CustomFeeAttribute__c Is Not Null AND LineItem.CustomFeeAttribute__c > 0
If the evaluated field relies on a record-triggered flow, verify that the automation commits its data to the database before the pricing request initializes.
Go to the Simulation tab, input a test payload where the target attribute is explicitly left blank, and click Run Test. Ensure the procedure completes successfully without throwing an exception.
Save your changes. Create a new version of the pricing procedure, set its status to Active, and give it the highest rank in your system.
Success: Your pricing pipeline is now secure against null pointer errors.
| Filter Root Cause Pattern | Observed Failure Behavior | Corrective Action Pattern |
| Incorrect Operator Sequence | Hard engine crash with an MVEL list filter execution failed message. | Move the ISNOTNULL clause to the absolute left side of the condition statement. |
| Blank Cross-Object Formulas | Downstream failure showing TagData.getTagValue() is null. | Apply a protective null check before passing the lookup attribute into matrix inputs. |
005389420

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.