If you’ve noticed some out-of-date Salesforce data in your data warehouse, we recommend checking to see if the field in question is a formula field.
Formula fields are algorithms that derive their value from other fields, expressions, or values. These fields can automatically calculate their value based on other fields.
Impact on Data Freshness
A formula field that’s calculated with another object’s modification stamp might not cause the field Stitch is using as the Replication Key to change. This means that Stitch may not always identify formula fields as having new values.
For example: Opportunity.Custom_Field_Account_Name__c is an opportunity field that calculates the Account Name. If the Account Name changes, Salesforce may not indicate that the Opportunity formula field has changed, meaning the Opportunity record won’t be detected by an incremental update.
Workarounds for Formula Fields
- If you’re using it as a join, you could recreate the join using SQL.
- If the field isn’t a join, depending on what you need, you could still recreate it using SQL or change the field to be a native field that’s updated through a workflow or apex trigger.
- Configure the table to use Full Table Replication. Note: This will increase the integration’s consumption of Salesforce API quota, as well as your Stitch row usage.
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.