Conditional Custom Fields for Opportunities

Conditional Custom Fields let Admins control which opportunity fields appear and which fields must be completed based on a deal’s pipeline, stage, status, or other field values.

This keeps opportunity forms focused and helps teams collect the right information at the right point in the sales process.

How Conditional Rules Work

Each conditional rule contains:

• The conditions that activate the rule.
• The fields or folders that appear or become mandatory when the conditions are met.

Supported triggers include:

• Pipeline
• Pipeline Stage
• Status
• Dropdown fields
• Radio fields
• Checkbox fields
• Multi-select fields

Available outcomes include:

• Displays an individual opportunity field.
• Displays an entire folder of opportunity fields.
• Requires a visible field to be completed before the opportunity can be saved.

For example, you can show additional onboarding fields when an opportunity is Won or require proposal details when it reaches a particular pipeline stage.

How to Enable Conditional Custom Fields

If the feature is not already enabled:

1. 1Go to.
2. 2Find.
3. 3Enable the feature for the sub-account.

Enabling the feature does not change existing opportunity forms. Conditional behavior begins after an Admin creates and saves the first rule.

How to Create a Conditional Rule

1. 1Go to.
2. 2Select.
3. 3Open the tab.
4. 4Click.
5. 5Select the field that should trigger the rule.
6. 6Choose an operator and trigger value.
7. 7Add more conditions if needed.
8. 8Connect multiple conditions using or logic.
9. 9Add one or more outcomes.

10.Review the rule using the live preview.

11.Click.

The rule becomes active immediately after it is saved.

Using AND and OR Conditions

Use AND when every condition must be met.

Example:

• Pipeline is Sales Pipeline
• Pipeline Stage is Closed

Use OR when any condition can activate the rule.

Example:

• Pipeline Stage is Proposal Sent
• Pipeline Stage is Closed

Use the live preview to confirm the expected behavior before saving the rule.

Showing Fields and Folders

Fields and folders included in a Show outcome are hidden by default. They appear only when the rule’s trigger conditions are met.

Fields that are not included in a Show rule remain visible as usual.

To show a field or folder conditionally:

1. 1Configure the rule’s trigger conditions.
2. 2Under, select or.
3. 3Select the field or folder.
4. 4Review the live preview.
5. 5Save the rule.

Making Fields Mandatory

A Make mandatory outcome requires users to complete a visible field before saving an opportunity.

Example:

• Pipeline Stage is Closed

When a user moves an opportunity to the Closed stage, the applicable fields must be completed before the change can be saved.

Important: A mandatory outcome does not automatically display a hidden field. If a field is controlled by a

Show rule, make sure its visibility conditions allow it to appear when required.

How to Manage Existing Rules

Go to Settings → Custom Fields → Opportunity → Conditional Rules.

From this page, Admins can:

• View a rule’s triggers and outcomes.
• Search for an existing rule.
• Edit a rule.
• Delete a rule.
• Create additional rules.

Changes take effect as soon as the rule is saved.

How to Manage Rules from the Pipelines Page

Pipeline-specific rules can also be managed from the Pipelines page.

1. 1Go to.
2. 2Find the required pipeline.
3. 3Open its menu.
4. 4Select.
5. 5Create or update the rule.
6. 6Review the live preview.
7. 7Click.

Important Notes and Limitations

• Only Admins can create, edit, or delete conditional rules.
• Rules are configured separately for each sub-account.
• Rules work when users add, edit, or bulk-edit opportunities on web and mobile.
• Fields and folders included in a Show outcome remain hidden until the conditions are met.
• Fields not included in a Show rule remain visible.
• Hidden fields retain their existing values.
• Hidden fields are excluded from mandatory validation.
• If multiple rules apply, their mandatory requirements are combined.
• Conditional validation does not apply to Public API or workflow-based updates.

Frequently Asked Questions

Why is a field still visible when the rule conditions are not met?

A field is hidden by default only when it is included in a Show field or Show folder outcome. Fields not included in a Show rule remain visible.

What happens to an existing value when its field becomes hidden?

The value is retained. Hiding a field does not remove or change its existing data.

Are hidden fields included in mandatory validation?

No. A hidden field is excluded from mandatory validation until it becomes visible.

What happens when multiple rules apply to an opportunity?

The applicable outcomes are combined. Users must complete all visible fields made mandatory by those rules.

Why is a conditional field not appearing?

Confirm that:

• The feature is enabled.
• The rule has been saved.
• The opportunity matches the rule’s trigger conditions.
• The correct pipeline, stage, status, or field value is selected.
• The field or folder is included in a Show outcome.

Do conditional rules apply to API and workflow updates?

Conditional validation applies to supported saves on web and mobile. It does not apply to Public API or workflow-based updates.