In the Spiff and Salesforce integration, if a formula field is updated and pulling into Spiff, the value and SystemModStamp field may not automatically update.
The 'SystemModstamp' is the date and time when a record was last modified by a User or by an automated process (such as a trigger.) In this context, 'trigger' refers to Salesforce code that runs to implement standard functionality, rather than an 'Apex trigger.' However, Derived fields, such as Formulas, do not have the Create or Update supported calls so they cannot be updated manually as well, hence the LastModifiedDate of the record will also not change for the associated record.
Due to the following reasons, the Formula/Calculated fields in Salesforce do not update the SystemModStamp:
Formula/Calculated fields are derived fields, meaning their values are computed based on other fields or data. They do not directly store data in the database but are dynamically calculated when accessed.
The SystemModStamp field is updated when a record is modified by a user or an automated process (e.g., triggers, workflows). However, changes in formula/calculated fields do not count as direct modifications to the record itself, as they are not stored in the database.
If a formula/calculated field depends on values from another object or field, changes to those source values will not trigger an update to the SystemModStamp of the record containing the formula/calculated field. The SystemModStamp only reflects changes to the record where it resides.
Salesforce optimizes performance by not updating SystemModStamp for formula/calculated fields, as these fields are recalculated on-the-fly and do not require database updates.
This article explains why Spiff may not reflect updated formula field values from Salesforce, and how to work around that limitation.
We recommend using one of the below options:
005239151

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.