Episerver - update 347

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.

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

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.

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.

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 http://quicksilver.ging.ep.se/episerver/EPiServer.Commerce.Shell/Stores/facet/campaignFacet?facetString=... returns HTTP 500 (YSOD screenshot attached).

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)

cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
cart.GetFirstForm().Shipments.Clear();
cart.GetFirstForm().Shipments.Add(orderGroupFactory.CreateShipment(cart)); // Expected shipmentId is -2, which it is
orderRepository.Save(cart);
cart = orderRepository.LoadOrCreateCart<ICart>(CustomerContext.Current.CurrentContactId, "Default", currentMarket);
cart.GetFirstForm().Shipments.Add(orderGroupFactory.CreateShipment(cart));
//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
cart.GetFirstForm().Shipments.Add(orderGroupFactory.CreateShipment(cart));
// This shipment gets id -3 which is fine