pricing-wiring

Deploy in this sequence: refresh decision tables, ensure core recipe mappings, deploy core procedures, ensure feature mappings, deploy feature procedures, apply context updates, then apply plan overlays. This prevents lookup table validation failures caused by missing prerequisites.

This error occurs when the PricingRecipeTableMapping row is missing even though the decision table exists and is active. Check placeholder resolution, decision table existence, the recipe-to-table mapping row, and the mapping component type in that order.

Decision tables are point-in-time snapshots, so rows written after the last refresh are invisible to pricing. Compare each table's LastSyncDate against its own source object's MAX(LastModifiedDate), reproducing the table's source criteria, and run a refresh task if stale.

No, expression sets containing __LOOKUPID_*__ placeholder tokens fail via raw sf project deploy because placeholders are not valid record IDs. Use cci task run deploy_expression_sets, which applies find_replace transforms to resolve placeholders to real DecisionTable IDs first.

A lookup step without CurrencyIsoCode as an input matches the first row regardless of currency, silently returning a plausible but wrong price. Add CurrencyIsoCode to every lookup step resolving currency-denominated values and wire currency inheritance via before-save flows.

Use the expression-sets skill for authoring or CRUD'ing pricing procedures themselves, including Connect API versus Metadata API choices and the activation lifecycle. Use pricing-wiring for where that work fits in the pricing layering model and flow order.