---
schema_version: "1"
id: 5468ddf4b7f26f81b66c808a09e15fc1cdce8d1efefd292de899c5511c91a043
title: Considerations for Creating Decision Tables
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/decision_table_limits.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.decision_table_limits.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ce9e6f81b10e7ecd940190c927abdb515b7a367ed1a6f9473e0cedb7f7161b90
description: Before you plan and create decision tables in your Salesforce org, review these considerations.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Considerations for Creating Decision Tables

Before you plan and create decision tables in your Salesforce org, review these considerations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions for clouds that have Business Rules Engine enabled</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-business_rules_engine-264-0-0-production-enus/b2d6dd5c-c231-428b-abbf-3dd2cd51a11f/images/icon_note.png)

Note If you use decision tables as part of Loyalty Management or Rebate Management, see [Decision Table](https://help.salesforce.com/s/articleView?id=ind.concept_decision_table.htm&type=5&language=en_US).

- You can use only the objects that have the CreatedDate and IsDeleted fields as source objects to create a decision table.
- You can group a table’s rows by up to two input fields that use the Equals operator.
- You can use a field’s sequence number only once in a custom logic.
    
    For example, the custom logic `(1 AND 2) OR (1 AND 3)` is invalid. Instead, define the logic as `1 AND (2 OR 3).`
- By default, a decision table can have 30 input fields and five output fields.
    
    Configure input fields so that during lookup, a maximum of 10 input fields are considered. This field aggregation can be achieved by using the AND operator in the table's input condition logic to join up to 21 required columns that use the Equals operator.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-business_rules_engine-264-0-0-production-enus/b2d6dd5c-c231-428b-abbf-3dd2cd51a11f/images/icon_example.png)

Example Configure a Decision Table Logic to Bring Input Columns Down to 10

A table has seven required input fields that use the Equals operator.

Here’s how the table’s input condition logic is configured.

```
(1 AND 2 AND 3) OR 4 OR (5 AND 6 AND 7)
```

When the table is activated, fields 1, 2, and 3 are joined and considered as one field. Field 4 is considered as an independent field. Fields 5, 6, and 7 are joined and considered as one field.

During lookup, even though the active table is considered to have three input fields, you can pass input values for all seven input fields. The output is based on the values passed for the seven input fields.