You are here:
Considerations for Overwriting Rep Statements
When overwriting a calculation or data in a rep’s statement in Salesforce Spiff, keep these considerations in mind.
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 |
- Spiff doesn’t support overwrites in statements that exceed 35 MB.
- When you overwrite data on the rep statement page, the change applies only to that particular rep in that particular period. Potential future calculations that sum data, such as quota attainment and QTD sales, don’t show the overwritten value.
- When you overwrite data from the Data Sources page, the change applies to the entire company. Any other reps that use the overwritten data see the changes in their calculations.
- Overwriting a calculation can affect tracing capability.
- A list of overwrites and overwrite statuses is available from the Admin | Overwrites menu. From here, search and manage all overwrites made by any admin in the company. To clear an overwrite with an Active status, click the three dots and select Delete Overwrite. Deleting an overwrite doesn’t remove it from the log, but clears the overwritten value and restores it to the synced or uploaded value.
Overwriting Data Types
To maintain accuracy and consistency in your compensation plans, each data type requires a slightly different approach for overwriting.
| Data Type | Considerations |
|---|---|
| Percentages | Make sure that the value is a decimal. For example, for a value of 5%, enter 0.05, not 5. |
| Dates | Make sure that the data remains in sync with time-sensitive rules. Follow the YYYY-MM-DD format for clarity, system compatibility, and consistency across all rules and calculations. |
| Boolean values | Make sure that you understand how changing the Boolean value triggers other actions or rules in compensation plans. |
| Custom data types | Make sure that you understand how these fields interact with the rest of your data model. Follow specific formatting guidelines for these custom fields, such as numeric ranges, text limits, or predefined formats or options. |
When an admin overwrites a non-currency field, an error can occur because Spiff interprets the overwrite value as a string, not a number. Spiff can’t use math functions on a string value. To error-proof an overwrite field, wrap it so that Spiff can read the value as a string or other original data type. In Designer, find every instance of the overwritten field and wrap it with the concat([]) function. Wrap concat([]) in whatever data type Spiff expects, usually number() or date().
= ThingToAddToOverwrittenField + number(concat([FieldTheAdminWantsToOverwrite]))Did this article solve your issue?
Let us know so we can improve!
