Package v20.22 - 13 April 2026

This release introduces a per-record sync opt-in mechanism for standard Salesforce objects — a capability aimed at enterprise organizations with large volumes of records that are unrelated to StoreConnect and do not need to be synchronized. It also fixes a bug in the Console Picklist Updater that was causing all picklist values to appear as new in subscriber organizations.

Breaking changes and cautions

No breaking changes in this release. The per-record sync opt-in is fully backward compatible — if the opt-in field is not present on an object, all records for that object continue to sync as they did before.

:::warning Store-created records require the opt-in value to be set via automation. When StoreConnect creates a record in Salesforce (a “fromStore” insert), it bypasses opt-in filtering for that initial insert — so the record is created regardless. However, any subsequent updates or deletes triggered from Salesforce on that record will be subject to opt-in filtering. If you enable the StoreConnect_Sync__c opt-in field on a standard object, ensure store-created records have their StoreConnect_Sync__c field set to enable_sync automatically — via a default field value, a trigger, or a Flow — otherwise those records may stop syncing after they are created. [PKG-8110] :::

Enhancements

Per-record sync opt-in for standard Salesforce objects [PKG-8093, PKG-8110] Organizations with large volumes of standard Salesforce object records — such as millions of Accounts — can now control which records participate in StoreConnect synchronization on a per-record basis. This prevents unnecessary sync activity for records that have no relationship to StoreConnect.

To enable opt-in filtering for a standard object: 1. Create a text field named StoreConnect_Sync__c on the standard object in Salesforce Setup. 2. Once the field exists, only records where the value of StoreConnect_Sync__c is enable_sync will be included in StoreConnect synchronization. 3. Records where the field is blank or absent will not generate sync events.

If you do not create the field on an object, all records for that object continue to sync as before — there is no change to existing behavior. Custom objects are not affected by this feature. To disable opt-in filtering on an object, delete the StoreConnect_Sync__c field and all records will resume syncing automatically.

Opt-in filtering applies consistently across all sync paths: trigger-based sync, batch jobs, poll processing, and manual invocable sync actions all respect the opt-in field.

Deprecated fields

No fields have been formally deprecated in this release.

Fixed bugs

Console Picklist Updater showing all values as “NEW” [PKG-8102] In subscriber organizations where picklist fields had been customized — for example, extra values added, labels translated, or defaults changed — the Console Picklist Updater was incorrectly displaying all picklist values as “NEW” with null data types. This made it appear as though all values needed to be updated, even when no actual changes were required.

The root cause was a Salesforce Metadata API limit of 10 items per call. When StoreConnect has more than 10 out-of-sync picklist fields to check (common in customized orgs), the single unbatched API call exceeded the limit, returned an empty result, and the tool compared the installed schema against empty data — marking every value as new. The Picklist Updater now batches Metadata API calls correctly in groups of 10, and picklist values are compared accurately against what is installed in the org.