Skip to content

Commit 4d0835e

Browse files
authored
Update index.md
Added context about historical data and how customers can self-serve syncing their collections
1 parent d46e61e commit 4d0835e

File tree

1 file changed

+11
-1
lines changed
  • src/connections/sources/catalog/cloud-apps/salesforce

1 file changed

+11
-1
lines changed

src/connections/sources/catalog/cloud-apps/salesforce/index.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,12 +107,22 @@ Segment does not support hard deletes in Salesforce. Use of hard deletes will re
107107

108108
## Collection Properties
109109

110-
Segment performs a one-to-one mapping of all publicly available fields (standard and custom) from Salesforce. To see the full list of the standard fields refer to the Salesforce field documentation linked in each collection above. If you've added and selected custom fields to an existing collection, [contact Segment Support](https://segment.com/help/contact/) to configure them to sync. You do not need to include the field names.
110+
Segment performs a one-to-one mapping of all publicly available fields (standard and custom) from Salesforce. To see the full list of the standard fields refer to the Salesforce field documentation linked in each collection above.
111111

112112
## Adding Destinations
113113

114114
Warehouses are the only supported destination for object-cloud sources.
115115

116+
## Historical Data
117+
When a new Object/Collection is enabled, Segment automatically runs a full historical re-sync on that Object.
118+
119+
However, for custom properties/columns, Segment only populates the custom property with data that comes in after the custom field was enabled. In order to populate the new custom field(s) for records that have previously been synced, a manual re-sync needs to be initated.
120+
121+
For Salesfroce, Segment uses the `SystemModstamp`(system_modstamp) field to checkpoint collections that sync incrementally. When it is enabled, we sync collections incrementally. When it is disabled, we sync collections fully. If you would like to force a collection to sync fully on the next run to bring in historical data, you can disable the `SystemModstamp` field on the collection, allow the next sync to complete and then re-enable `SystemModstamp` so the collection syncs incrementally in the coming syncs.
122+
123+
If you've added and selected custom fields to an existing collection and would not like to use the SystemModstamp to bring in historical data, please feel free to [contact Segment Support](https://segment.com/help/contact/) to configure them to sync. You do not need to include the field names.
124+
125+
116126
## Troubleshooting
117127

118128
If you are syncing data from a Salesforce sandbox environment and see an "Invalid credentials" error, [contact Segment Support](https://segment.com/help/contact/), who will configure your Segment source to use sandbox data.

0 commit comments

Comments
 (0)