March 2023 Release

  • Updated

Release: 5.1.2303.3221

There is a new build number for this release. We reverted using the translation icon for translating attribute names and labels as it caused unexpected translations to appear within the filters compared to the attributes on product records. This build also contains Square saved cards functionality, a fix for broken CMS fields, and a fix to prevent integration jobs importing a significant volume of data from failing with a storage error.

There is a high-risk breaking change for Spire CMS. See below for more information.

The following is a list of the bug fixes and enhancements provided in the March 2023 Release. Some of the bug fixes listed below may address existing Support Articles. A comprehensive list is at the bottom of this page.

The March 2023 release is now available for developers to pull down and work with locally or to request for deployments.

March 2023 release highlights

  • You can now set the default variant at the product level, rather than at the variant trait level. This feature allows you to set a child product as the default variant, which is useful if you have different variant products with the same variant traits.
  • You can now configure Full Width using Site Configurations in the Style Guide
  • You can now add code to <head> directly within the Style Guide. You can use this to connect to other products like Web Experimentation. 

Important notes/Breaking changes

Optimizely recently discovered that setting the Delete Behavior Action in the job step configuration to Delete Record results in incorrect functionality. Although this issue has existed for an undetermined amount of time, it has been resolved with the March 2023 release. To ensure that our customers and partners are fully aware of this change, please note that the Delete Record option of the Delete Behavior Action setting will now do the following:

If the Action setting has a value of Delete Record and Use Delta Dataset has a value of No, then the job deletes all items for the given dataset from Configured Commerce unless the data import contains the items. You can manage this further with the Run Options Max Deactivation % setting on the job definition, which identifies a limit (%) for the number of deletes and will not delete any if that limit is reached during one run.

High risk breaking changes for Spire:

  • Upgraded Typescript from 3.7.1-rc to 4.9.4
    • There are several new rules that have been added between these versions. Partners will likely see errors related to these new rules in their build output. These issues will need to be resolved on a case-by-case basis.
    • There is a new TypeScript rule that requires targets of the 'delete' operator to be optional. This required changing the logic for 'cleaning' API models in some of the Spire handlers. The TypeScript linter will most likely call these instances out in partner code. Partners should review any places in their code that reference a variable whose logic for a 'delete' operation is changed.
    • TypeScript 4.9.4 has new typings for the Google Analytics objects. Any custom Google Analytics implementations might need to be updated.
    • TypeScript 4.9.4 removed Internet Explorer types from the global Navigator interface. Since IE is not supported by Configured Commerce, references to those values in base code have been removed.

Low risk breaking changes:

  • Moved AdminActionPermissionType into the Insite.Data.Entities namespace after discovering it was not in one. Converted to file scoped namespaces. This is a breaking change that may recover recompiling and adding using statements. It is unlikely that AdminActionPermissionType is used in any Extensions.
  • Added new IDeleteProcessor.Execute method, which takes an additional parameter IDictionary<string, string> additionalParameters. This was done to pass the firstTimeDeltaSetJobRun variable from JobPostprocessorFieldMap.
  • Got Classic AUI tests running in net6, which were missed when replacing HttpContext stuff with IHttpContextProvider to make it compatible with both net48 and net7.

Partners/Developers: You can view a cumulative list of breaking changes, including Spire breaking changes, at the bottom of this page. (Note the two tabs at the bottom of the spreadsheet: one for cumulative breaking changes, one for Spire breaking changes.)

Database changes/Updates


Bug fixes