---
schema_version: "1"
id: 85fe8501ae071129b7d531b83f96417923dc9932b063e0b0c4177daa798b9dbd
title: Salesforce Spiff Release Notes for March 13, 2026
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/rn_spiff_2026_mar_13.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.rn_spiff_2026_mar_13.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 01b23ed31cf9df02a56f96f4dde9948f5f5704e2d3e29201440857a8fda83125
description: Create an isolated environment to update commission logic and custom reports and to test new features without risking your production data. Use a change set to review, validate, and merge verified updates from your sandbox into your production environment.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Salesforce Spiff Release Notes for March 13, 2026

Create an isolated environment to update commission logic and custom reports and to test new features without risking your production data. Use a change set to review, validate, and merge verified updates from your sandbox into your production environment.

## Safely Test Changes in a Salesforce Spiff Sandbox

Protect your production environment by using a Salesforce Spiff sandbox to update commission logic and test new features. The sandbox replicates your production environment’s commission rules and reporting structures, but doesn’t include transactional data and sensitive information. Sandboxes provide a secure workflow that aligns with standard change management best practices so that you can validate updates before applying the changes to live data. You can create up to two sandboxes per production environment.

**Where:** This change applies to Salesforce Spiff.

**How:** In your production environment, go to **Admin** | **Settings**.

Spiff creates sandboxes as replicas of your production environment’s logic, including commission rules and reporting structures but excluding transactional data, such as users and sensitive keys.

- Grant specific users access to the sandbox by mapping their production roles to the new environment.
- Track modifications in your sandbox and bundle them into change sets of up to 2,000 changes.
- Before committing changes, you can run a technical dry run to check for database merge collisions. After you approve a change set, you deploy the change set to merge the updates into your production environment.

During the deployment process, Spiff blocks modifications to prevent data conflicts, and a user with Designer permissions needs to enter Designer to finalize the merge.