pricing-wiring

Wire Revenue Cloud pricing recipes, procedure plans, and feature overlays in dependency order.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill pricing-wiring-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pricing-wiring
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/pricing-wiring
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill pricing-wiring-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pricing changes in Salesforce Revenue Cloud span recipes, recipe-table mappings, expression set procedures, procedure plans, and context definitions, and deploying them in the wrong order causes silent lookup failures, locked active versions, and stale decision tables. ## Core Features & Use Cases - Dependency-Ordered Layering: Separates core, feature, and overlay prerequisites so recipe mappings, procedures, and plan overlays deploy in a safe sequence. - Procedure Plan Overlays: Applies JSON-driven plan overlays with deactivate, resequence, verify, and reactivate steps using anchor-based placement. - Staleness and Troubleshooting Guides: Diagnoses decision-table staleness from runtime-created pricing rows and provides a symptom-first decision tree for deploy and lookup errors. - Use Case: When adding a PRM pricing feature pack, wire its recipe-table mapping task before the expression set deploy, apply context plan updates, then run the overlay and verification tasks idempotently. ## Quick Start Use the pricing-wiring skill to plan the deployment order for a new Revenue Cloud pricing feature that adds recipe mappings, procedures, and a procedure plan overlay.

Frequently Asked Questions about pricing-wiring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Revenue Cloud pricing procedures in the right order?▼

Activate lookup artifacts first, then ensure core recipe mappings, deploy core procedures, add feature mappings, deploy feature procedures, apply context updates, and finish with plan overlays and verification. This ordering prevents lookup and activation-lock failures.

Why does my ListPrice lookup step fail even though the decision table exists?▼

The pricing recipe table mapping row is likely missing, so the recipe is not linked to the decision table. Run the recipe mapping configuration task and verify the PricingRecipeTableMapping row exists with the correct component type.

Why is a newly created contract price not reflected in pricing?▼

Decision tables are point-in-time snapshots, so rows written after the last refresh are invisible to lookups with no error. Compare each table's LastSyncDate against its source object's newest LastModifiedDate and run a refresh task if stale.

Can I deploy expression sets with sf project deploy directly?▼

No, expression sets containing __LOOKUPID_*__ placeholder tokens are rejected by the Metadata API as invalid record IDs. Use the CCI deploy_expression_sets task, which resolves placeholders to real DecisionTable IDs via find_replace transforms first.

Why does a pricing procedure deploy fail with a generic unexpected error?▼

An active ProcedurePlanDefinitionVersion referencing the expression set locks it from Metadata API updates. Deactivate the plan version first, deploy, then reactivate, and check for duplicate LookUpId parameters in a single step.

When should I use expression-sets instead of pricing-wiring?▼

Use expression-sets for authoring or CRUD'ing the pricing procedures themselves, including Connect API versus Metadata API mechanics. Use pricing-wiring for where that work fits into the pricing layering model and flow sequencing.