Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Episerver - update 347

Release summary

New releases of Episerver Commerce (CSR repeat last order, telemetry implemented for CSR) and Episerver Telemetry (telemetry added for Commerce CSR UI). Bug fixes for the Episerver Block Enhancements Labs add-on.

Released items December 15, 2020

Area ID Type Description Released
  CSR repeat past order

This time-saving feature allows customer service representatives to create new orders by "reusing" information in previous orders.

This is done by selecting an order, either from the Order list or from a customer, and selecting the Reorder option in the Order Management user interface.

EPiServer.Commerce 13.27.0; (Or a related package);
Dec 22, 2020
  Change "payment plans" to "subscriptions"

In the Order Management view in Episerver Commerce, "Payment plan" is changed to "Subscription" to align terminology.

EPiServer.Commerce 13.27.0; (Or a related package);
Dec 22, 2020
  Implement Telemetry for CSR

With the purpose to understand Episerver users better and effectivize resources so that we can deliver the best user experience possible and prioritize feature work, we are gathering some telemetry data from the CSR user interface. 

The data collected is completely anonymized and will only be used internally for decision making around user experience and feature development.

EPiServer.Commerce 13.27.0; (Or a related package);
Dec 22, 2020
  Unable to import second- (or third-) entry relations

Fixed issue with import of second and third entry relations in Commerce product catalogs.

The issue: If the parent entry already has a RelationType (for example "ProductVariation") existing for another item, any additional new relation from the import will not be added.

EPiServer.Commerce 13.27.0; (Or a related package);
Dec 22, 2020
  Issue with Marketing/Campaign which has no target market

Fixed issue with HTTP 500 error when filtering with CampaignFacet in the Commerce Marketing interface in scenarios with a campaign without any target market.

Environments: Reproduced with Quicksilver, Commerce v13.22.0, 13.23.1, 13.24.0.

Steps to reproduce:

  1. Create a new campaign.
  2. Edit "Target markets", uncheck all (change to None).
  3. Save and return to Campaign list.
  4. In left pane (under search field), select Campaign status => All and Market => Any
  5. The page goes blank, checking XHR requests, the call to returns HTTP 500 (YSOD screenshot attached).


EPiServer.Commerce 13.27.0; (Or a related package);
Dec 21, 2020
  OrderGroupFactory calculates shipping IDs incorrectly after upgrade

Fixed issue where OrderGroupFactory calculates shipping IDs incorrectly after upgrade.

For the multiple order forms in cart as the below code, the CreateShipment() are returning same ShipmentId (-2). See comments in code.

Code to reproduce:
var orderRepository = ServiceLocator.Current.GetInstance<IOrderRepository>();
var orderGroupFactory = ServiceLocator.Current.GetInstance<IOrderGroupFactory>();
var currentMarket = ServiceLocator.Current.GetInstance<ICurrentMarket>();
ICart cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
if (cart != null)

{ orderRepository.Delete(cart.OrderLink); }

cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
cart.GetFirstForm().Shipments.Add(orderGroupFactory.CreateShipment(cart)); // Expected shipmentId is -2, which it is
cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
//Expected shipmentId is -3 which it is in 13.18.2, but in 13.26.0 this is assigned -2 which leaves us with two shipments with the same id
// This shipment gets id -3 which is fine

EPiServer.Commerce 13.27.0; (Or a related package);
Dec 21, 2020

More on releases

Related topics

Last updated: Dec 22, 2020