Decision Tables in Revenue Cloud

But what exactly are decision tables, and why is it so important to keep them refreshed?

"Let’s break it down."

What Are Decision Tables?

Think of decision tables as smart lookup tables. Instead of hardcoding business logic into Apex or using complex flows, Revenue Cloud lets you define rules in structured tables that can be easily managed and scaled.

What They Do:

✔ Store Business Rules

Whether it’s qualifying a product for a bundle or applying a volume discount, rules live here.

✔ Evaluate Inputs

Each row represents a rule. The system matches input data (like product, quantity, or region) against these rows and returns outcomes like price, qualification status, or rating.

✔ Power Core Procedures (Used In)

• Qualification & Disqualification
• List and Attribute-Based Pricing
• Volume or Tier Discounts
• Usage-Based Pricing Calculations

✔ Support Multiple Matches

One set of inputs can return multiple rule matches, offering flexible pricing/qualification logic.

How Are They Built?

• Based on Salesforce standard or custom objects
• Columns = input criteria fields
• Rows = rule entries
• Outputs = matched results
• Cached like a snapshot of the source object for performance
• Each use case (qualification, discount, rate, etc.) typically gets its own table

Limit Alert: Salesforce allows up to 1000 decision tables per org by default, and standard tables may cap out around 100k records (Advanced tables can scale much higher).

Why and When to Refresh Decision Tables

Here’s the catch: decision tables don’t auto-update when the source data changes. They act as a snapshot. So if you update data (like pricing, rules, product attributes), your decision table won’t reflect those changes until you refresh it.

Common Triggers for a Refresh:

✔ Rule or Field Changes

• Added/edited rules in the decision table
• Added new fields to the source object

✔ Product Data Updates

• New products or category changes
• Attribute value changes

✔ Pricing Configuration Updates

• New or updated volume/tier/attribute discounts
• Derived pricing records added

✔ Formula Fields in Use

• If using dynamic formulas (like TODAY()), daily refreshes are ideal

✔ Post-Deployment or Org Upgrade

• Always refresh after major releases or configuration deployments

✔ Troubleshooting Issues

• Unexpected behavior in pricing or product visibility? Refresh the decision tables first.

How to Refresh Decision Tables in RLM?

Salesforce gives you a few ways to keep your decision tables up to date:

1. “Sync Pricing” Button

• Found in Salesforce Pricing Setup
• Triggers refreshes for pricing-related tables
• Limit: 20 refreshes per hour (each click may refresh multiple tables)

2. Manual Refresh

• Navigate to the decision table and click “Refresh”
• Best for targeting specific updates without hitting limits

3. Automated Flow

• Use the Decision Table Refresh Action in Flows
• Can be scheduled or event-triggered
• Not bound by hourly limits (ideal for daily sync jobs)

4. During Deployments

• Use tools like SFDMU or Prodly to deploy decision tables
• Always deploy custom fields before the decision tables that depend on them

Which Decision Tables Should You Refresh?

Here’s a cheat sheet depending on what you’re working on:

Pro Tips

• Use Flows to automate daily or post-deployment refreshes
• Create a refresh checklist for deployments and upgrades
• Avoid overusing “Sync Pricing” to stay under rate limits
• Document which procedures depend on which tables—makes troubleshooting faster

Final Thoughts

Decision tables are one of the most powerful tools in Revenue Cloud’s arsenal—but only if they’re accurate. Understanding when and how to refresh them will save you hours of troubleshooting and ensure your pricing and qualification logic always runs as expected.