Skip to content
Log in

Package v20.11 - 1 December 2025

On this page

This release improves URL routing reliability, fixes payment processing errors in Salesforce-hosted environments, and resolves stock level field permissions that were causing inventory inaccuracies. The POS layout has been extended with new fields to support custom actions. A fix to the product importer ensures products without images are no longer skipped when media field mappings are configured.

Field and object changes

The following new fields, values, and objects were added to this version of StoreConnect. Not all of them automatically appear in your org when you upgrade, and they never appear on page layouts or record pages your org has customized. Refer to the relevant procedure to add them.

New fields on existing objects

Object Field API name Type What it records Where it appears after upgrading
POS Layout Identifier s_c__Identifier__c Text Where the layout is placed in the POS Nowhere. Add it to your POS Layout record page
POS Layout Primary Action Item s_c__Primary_Pos_Action_Item_Id__c Lookup (POS Action Item) The button at the bottom of the layout Nowhere. Add it to your POS Layout record page
POS Layout Record Action Item s_c__Record_Pos_Action_Item_Id__c Lookup (POS Action Item) The action run when a record in a list layout is selected Nowhere. Add it to your POS Layout record page
POS Layout Secondary Action Item s_c__Secondary_Pos_Action_Item_Id__c Lookup (POS Action Item) The button at the top left of the layout Nowhere. Add it to your POS Layout record page
POS Layout Field POS View s_c__Pos_View_Id__c Lookup (POS View) A POS view to show in place of the field value Nowhere. Add it to your POS Layout Field layout
Stock Level Available to Sell s_c__Available_To_Sell_Formula__c Number Read-only quantity available to sell Nowhere. Add it to your Stock Level layout
Stock Level Count on Hand s_c__Count_On_Hand_Formula__c Number Read-only quantity on hand Nowhere. Add it to your Stock Level layout

Enhancements

POS Layout: New Fields for Custom Actions POS Layouts now include an Identifier field, a dedicated Actions section with Record, Primary, and Secondary Action Item fields, and a Position field on related lists. These additions provide greater flexibility when configuring custom actions in POS views.

Route Mapping: Automatic Generation on Slug and Path Changes Route mappings are now automatically generated whenever the path or slug of a product, page, article, article category, or product category is updated in Salesforce. This ensures redirects and URL mappings stay current without requiring manual updates, and uniqueness validation prevents conflicting or circular redirect paths from being created.

Deprecated Fields

No deprecated fields in this release.

Fixed Bugs

Payment Form: Errors from Salesforce-Hosted iframes When a payment form or other component was embedded in a Salesforce-hosted iframe (such as on a record page), the system was incorrectly flagging internal Salesforce postMessage communications as unknown and potentially dangerous. This produced errors such as “Cannot Take Payment: Unknown post message source” for Salesforce domain URLs. Salesforce-origin messages are now correctly identified and silently ignored, preventing false-positive errors that blocked payment interactions.

Stock Levels: Count On Hand and Available To Sell Fields Now Read-Only The “Count On Hand” and “Available To Sell” fields on Stock Level records were editable by administrators, which frequently caused incorrect inventory adjustments. Editing these fields directly does not account for the system’s calculated values, meaning any manual changes would be overwritten on the next transaction. These fields are now read-only formula fields. Stock quantities should be adjusted using the correct Change Qty field.

Product Importer: Products Without Images No Longer Skipped When importing products where media field mappings were configured but some products had no image data, the importer was attempting to create media records for the empty fields rather than skipping them. This caused partial imports where products without images failed to import at all. The importer now correctly skips media record creation when the key fields (name or URL) are blank.

Was this article helpful?

Was this article helpful?