Package v20.23 - 17 April 2026
On this page
This patch release extends the per-record sync opt-in mechanism — introduced in v20.22 — to support picklist fields on standard Salesforce objects. Administrators who prefer the controlled value set and improved user experience of a picklist field can now use one to manage sync opt-in, in addition to the existing text and text area options.
Breaking changes and cautions
:::warning
Organizations with a pre-existing picklist StoreConnect_Sync__c field will see a behavior change on upgrade. Before v20.23, if the StoreConnect_Sync__c field was created as a picklist type, the opt-in mechanism silently treated it as unsupported — meaning all records for that object synced, regardless of the field value. After upgrading to v20.23, opt-in filtering becomes active for picklist fields. Only records where StoreConnect_Sync__c equals enable_sync will sync. Before upgrading, verify that the enable_sync picklist value exists on the field and that all records intended to sync have that value set. [PKG-8184]
:::
Enhancements
Picklist field support for per-record sync opt-in [PKG-8184]
The StoreConnect_Sync__c opt-in field used to control per-record sync eligibility on standard Salesforce objects now supports picklist field type, in addition to the existing text and text area types. Administrators can create StoreConnect_Sync__c as a picklist field with enable_sync as a value, then set that value on records that should participate in synchronization. Records without the value set will be excluded from sync.
Existing implementations using a text or text area field are unchanged. Note that multi-select picklist fields are not supported — only single-select picklist fields work with opt-in filtering.
Deprecated fields
No fields have been formally deprecated in this release.
Fixed bugs
No bug fixes in this release.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.