Loading
Salesforce now sends email only from verified domains. Read More
Sales Performance Management
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Options for Dynamic Data in Salesforce Spiff Plans

            You are here:

            1. Salesforce Help
            2. Docs
            3. Sales Performance Management

            Options for Dynamic Data in Salesforce Spiff Plans

            In Salesforce Spiff, manage plans more efficiently by making some fields dynamic instead of static. To help you choose the best options, review pros and cons.

            Required Editions

            Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
            Available in: Enterprise, Unlimited, and Developer Editions
            Available for an additional cost in: Professional Edition with Web Services API Enabled
            Option Pros Cons
            OR filters for period changes Minimizes filter and rule maintenance. You don't have to create duplicate year-specific filters or duplicate year-specific rules, and you don't have to update filters assigned to rules or accumulated variables. Takes longer to process data and consumes more server resources. An OR filter isn't an ideal solution for large or complex data filters.
            vlookup function for value changes
            • Requires only future table updates, not logic updates.
            • Supports mid-period changes.
            • Takes longer to implement.
            • Requires every possible input, including years, in the table as a hard-coded value.
            • Requires some Designer knowledge for maintenance.
            range_lookup function for value changes
            • Requires only future table updates, not logic updates. If no changes occur in the future, no table updates are required.
            • Supports mid-period changes.
            • Requires only dates that changes occur, and doesn't require every possible input.
            • Takes longer to implement.
            • Requires some Designer knowledge for maintenance.
            • Isn't specific to individual reps.
            Quota tables for rate changes
            • Doesn't require Designer knowledge.
            • Supports quick updates for individual reps.
            • Supports only yearly, quarterly, or monthly changes.
            • Requires that you add new values regularly, even if there aren't changes.
            Plan assignment updates for rate changes
            • Doesn't require Designer knowledge.
            • Supports updates for individual reps by adding a plan assignment row for each rep whenever a change occurs.
            • Combines with other options, such as creating multiple range tables for specific reps or specific plans.
            		 Requires extra logic for mid-period changes to avoid double payment.
            Manual uploads for rate, value, or role changes
            • Represents the most dynamic option.
            • Supports multiple types of changes at once.
            • Requires only future uploads, not logic updates.
            • Takes longer to implement.
            • Requires knowledge of data practices and upload processes.
             
            Loading
            Salesforce Help | Article