pricing-wiring

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

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill pricing-wiring-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pricing-wiring
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/pricing-wiring
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill pricing-wiring-bgaldino

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 or with unresolved placeholders causes silent failures, generic deploy errors, and stale decision tables. ## Core Features & Use Cases - Dependency-Ordered Layering: Separates core, feature, and overlay layers so recipe mappings, procedures, and plan overlays deploy in a safe, idempotent sequence. - Placeholder and Lookup Strategy: Keeps metadata org-agnostic with __LOOKUPID_*__ and PAS placeholders resolved by deploy transforms, preferring LookUpApiName over hardcoded IDs. - Failure Diagnosis: Provides troubleshooting decision trees for lookup-table errors, multicurrency pricing mistakes, plan-version locks, stale decision tables, and context attribute failures. - Use Case: When adding a PRM pricing feature pack, wire the feature recipe-table mapping task before the expression set deploy, apply the procedure-plan overlay with anchor-based placement, and validate with the provided CCI flows and SOQL checks. ## Quick Start Ask the agent to wire a new pricing feature pack by creating the recipe-table mapping payload, deploying the pricing procedures, and applying the procedure-plan overlay in dependency order.

Frequently Asked Questions about pricing-wiring

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

FAQPage Schema
How do I deploy Salesforce pricing procedures in the correct 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. This ordering prevents lookup and dependency failures.

Why does my ListPrice step say the lookup table is invalid?

The decision table may exist but lack a recipe-table mapping row for the target pricing recipe. Check placeholder resolution, table existence, the PricingRecipeTableMapping row, and the mapping component type in that order.

Can I deploy expression sets with sf project deploy directly?

No, expression sets containing __LOOKUPID_*__ placeholder tokens fail because placeholders are not valid Salesforce record IDs. Use the cci deploy_expression_sets task, which resolves placeholders to real DecisionTable IDs via find_replace transforms first.

Why is my decision table returning stale pricing data?

Decision tables are point-in-time snapshots, so rows written after the last refresh are invisible to lookups. Compare each table's LastSyncDate against its own source object's newest LastModifiedDate, reproducing the table's source criteria.

What causes the generic unexpected error when deploying an expression set?

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 LookUpApiName versus LookUpId in pricing steps?

Default to LookUpApiName when the target DecisionTable DeveloperName is stable and verified. Add LookUpId placeholders only when a known org or runtime issue requires it, and never include both casually in one step.