PricingActionParameters in SFDX

Architectural Overview#

In Salesforce Revenue Cloud, Industries CPQ, and Revenue Lifecycle Management (RLM), dynamic pricing calculations require decoupled, high-performance execution. Pricing engines calculate list prices, volume discounts, tiered surcharges, and contractual adjustments via modular pricing procedures and calculation matrices.

The PricingActionParameters metadata type defines the formal interface contract between transactional records (e.g., Quotes, Orders, Assets) and pricing calculation engines. It establishes parameter names, data types, default values, and directional mapping (Input vs. Output).

By decoupling parameter contracts from UI logic, enterprise architects enable pricing strategies to evolve rapidly without requiring breaking code changes in quoting components or integration layers.

Directory and File Conventions#

In SFDX source projects, PricingActionParameters files are organized in the pricingActionParameters/ directory:

Key Metadata Fields#

The XML schema of PricingActionParameters controls parameter directionality and validation:

Declarative XML and Package Manifest Examples#

Below is an enterprise XML definition mapping a volume discount percentage parameter:

<?xml version="1.0" encoding="UTF-8"?>
<PricingActionParameters xmlns="http://soap.sforce.com/2006/04/metadata">
    <actionName>Enterprise_Hardware_Pricing_Procedure</actionName>
    <dataType>Percent</dataType>
    <description>Passes tier-based volume discount percentage back to quote line items.</description>
    <direction>Output</direction>
    <parameterName>VolumeDiscountPercent</parameterName>
</PricingActionParameters>

Package Manifest (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Volume_Discount_Param</members>
        <name>PricingActionParameters</name>
    </types>
    <version>68.0</version>
</Package>

CLI Retrieval and Deployment Commands#

Manage PricingActionParameters via the Salesforce CLI:

# Retrieve all pricing action parameters
sf project retrieve start --metadata PricingActionParameters

# Deploy specific pricing action parameters to sandbox
sf project deploy start --metadata "PricingActionParameters:Volume_Discount_Param"

# Validate parameter bindings before deployment
sf project deploy validate --metadata PricingActionParameters

Architect Best Practices and Gotchas#

• Strict Type Alignment: Ensure the dataType specified in PricingActionParameters matches the corresponding target CustomField on QuoteLineItem or OrderItem. Passing a Text parameter into a Currency field causes runtime calculation exceptions.
• Deployment Sequencing: Deploy underlying custom fields and calculation matrices before deploying PricingActionParameters and pricing procedures to avoid unresolved dependency errors.
• Bulk Transaction Performance: When designing calculation inputs, avoid passing unnecessary long text fields into pricing actions; keep payloads lean to optimize calculation throughput during large quote imports.

Frequently asked questions

What is the purpose of PricingActionParameters in Revenue Cloud?

It maps transactional data between cart or quote line items and calculation procedures, defining input and output data contracts.

Where are PricingActionParameters stored in an SFDX source project?

They reside in force-app/main/default/pricingActionParameters/ with the .pricingActionParameters-meta.xml suffix.

What data types are supported by PricingActionParameters?

Standard data types include Currency, Percent, Number, Text, Boolean, and complex Collection types.

Why does a pricing procedure fail when PricingActionParameters are deployed?

Failures typically occur when data types or parameter names in the procedure do not match the transactional field definitions on the line item.