Data Sync Settings
- 1 Max Sync Waves
- 2 Enable Full History Wave
- 3 Object History In Months
- 4 Objects that are subject to a stale record cleanup (due to changes in record accessibility/permissions)
- 5 Frequency of stale record cleanup (due to changes in record accessibility/permissions)
- 6 Frequency of stale record cleanup (due to changes in record accessibility/permissions)
- 7 Force the stale record cleanup stage to run on the user's next sync
- 8 Enable Reachability on Subsequent Passes
- 9 Object Filter Limit
- 10 Auto Sync Setting
- 11 Allow/Deny Sync through 3G/4G
- 12 Force a Layout Sync
- 13 Auto Sync Time Interval
- 14 Sync Data Filter using a "Where" Clause
- 15 Allow Base 64 Download
- 16 Allow Sync and display of Rich Text Field Images
- 17 Sync Objects - Last Modified Date Field Override
- 18 Pulsar Sync Object List
- 19 Pulsar Sync Objects - Relationship Directives
- 20 Sync In Progress Banner
- 21 Sync Banner Progress Bar Color
- 22 Sync Banner Progress Bar Background Color
- 23 Sync Banner Progress Bar Height
- 24 Enable Field Service Sync Setting
- 25 Forced Work Offline Mode (with Sync Enabled) Setting
- 26 Disable syncing listviews for certain object types
- 27 Remind users to sync periodically
- 28 Enable Content Document Direct Sync
- 29 Enable Chronological Changes
- 30 Configure Conflict Resolve Policy (Global)
- 31 Configure Conflict Resolve Policy (Object/Field Specific)
- 32 Available with version 13.0+
- 33 Configure Duplicates Policy
- 34 Enable Composite API
- 35 Enable Composite Graph API
- 36 Maximum Updates Per Object
- 37 Connect Timeout Seconds
- 38 Prevent Duplicate Create and Update Transmissions
- 39 Composite API Setting Usage
- 40 Bypass Failed Changes
- 41 Add Sync Window Seconds (to second pass)
- 42 Enable Sync Speed Measurement
- 43 Skip Catch-Up (Delta) Sync For Specific Objects
- 44 Force a re-sync of one or more tables on the user's next sync
- 45 Lightning quick action metadata sync where clause
|
|
|---|---|
Name | Max Sync Waves |
Key | pulsar.sync.maxWaves |
Value | A Positive Number |
Default Value (if any) | 24 |
Compatibility | iOS Windows Android |
Description | A sync wave is generally equivalent to one month of history, and with this numeric setting you may specify how many months into the past (in terms of active records) that the algorithm should look back and fetch them. Pulsar determines active records by using the LastModifiedDate, SystemModStamp, or another datetime field (if overridden with the pulsar.sync.objects.lastModifiedDateField Pulsar Setting). The first wave is calculated from the current timestamp back to the first day of the same month. This means that the first wave is often less than a full month’s worth of data. This is done to break up the remaining waves in simple month segments. For example, specifying 4 waves and performing an initial sync on December 5 will create one wave from December 1 to December 5, a second wave encompassing all of November, and a third wave encompassing all of October. The fourth and final wave will attempt to retrieve as much data as possible from September 30 to as far back as January 1, 1980. Please see the pulsar.sync.enableFullHistoryWave setting for more information on customizing the behavior of the final wave. |
Notes/Comments | To guarantee that a user should initially sync a specific number of months of historical data, you will need to add one or two to your number depending on how you’ve configured the final wave. For example, for a minimum of two years worth of data, you can specify 26 (with the full history wave enabled) or 25 (with the full history wave disabled). |