Loading
Slack 관련 문의처가 Salesforce Help로 통합 및 변경됩니다.더 많이 읽기

MVEL List Filter Execution Failed in Pricing Procedure

게시 일자: Aug 11, 2026
상세 설명

Common Symptoms & Error Variations

1. Hard System Halt (Advanced Evaluation Enabled)

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

2. Downstream Layer Failures

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.

Step-by-Step Configuration Update

 

1.Open Your Pricing Procedure Workspace:Requires Pricing Administrator permissions.

In the App Launcher, find and select Expression Sets (or Pricing Procedures) and open the specific active version that is generating the error.

 
2.Find the Targeted List Filter Element:Locate the failing logic block.

Locate the ListFilter or List Container element mentioned in your error logs or the step skipping your pricing logic.

 
3.Reorder the Filter Expression Criteria:Crucial: Put guards on the left.

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

4.Align Upstream Flow Triggers:Check background automation timing.

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.

 
5.Simulate and Test the Changes:Confirm the validation fix.

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.

 
6.Activate and Rank the New Version:Deploy the updated logic.

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.

Configuration Quick-Reference

Filter Root Cause PatternObserved Failure BehaviorCorrective Action Pattern
Incorrect Operator SequenceHard 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 FormulasDownstream failure showing TagData.getTagValue() is null.Apply a protective null check before passing the lookup attribute into matrix inputs.

Knowledge 기사 번호

005389420

 
로드 중
Salesforce Help | Article