Products
Packages [expand] [collapse]
Services
Released in version
5.4.5
5.4.4
5.4.3
5.4.2
5.4.1
5.4.0
5.3.1
5.3.0
5.2.0
5.1.0
5.0.1
5.0.0
4.2.1
4.2.0
4.1.0
4.0.0
3.0.1
3.0.0
2.1.1
2.1.0
2.0.10
2.0.9
2.0.8
2.0.7
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1

Release notes for Episerver updates

This overview lists changes included in Episerver updates delivered as NuGet packages and services. Use the information to decide which updates to apply to your project, see Installing Episerver updates. Select a product, package, or service in the left menu, and filter for dates, features, or bug fixes.

  • See only new features (all features) - filter on item type Feature.
  • See only end-user (user interface) features - filter on item type UI Feature.
  • See only critical bug fixes - filter on item type Critical Bug.

Note: New NuGet packages listed here may not be immediately available in the Episerver NuGet feed.

Changes in EPiServer.ServiceApi

Item type
From date
To date
Items/Page
Area Id Type Description Released
COM-11491
  ServiceAPI Get orders LineItems Properties null

Service Api v5.4.3
GET Endpoint /episerverapi/commerce/orders/

{ordergroupId}

In the result of the JSON, the LintItems always had an empty Properties Array; in the decompiled code from the dll, the properties would not be set in the LineItemModel.

Fix Version/s: EPiServer.ServiceApi 5.4.5;
Jun 30, 2020
COM-10733
  FOIA-Updating noderelations/ mode category under other category
Customer Impact Statement

Updating noderelations/mode category under another category.

Issue Description

The client is having a problem when deleting an existing NodeRelation.
More details:
First, to delete an existing NodeRelation, they need the ParentNodeCode and the ChildNodeCode.
They want to move it from an existing place to another, so they can see only the newParentCode,
not the existing ParentCode.
Here is the code:

GetJson($"/episerverapi/commerce/nodes/{nodeRelation.ChildNodeCode}/noderelations", out string result);

// result is empty -> we can not GET the nodeRelations from the childNode

 GetJson($"/episerverapi/commerce/nodes/{nodeRelation.ParentNodeCode}/noderelations", out string result);

// result is ok-> we can GET the nodeRelations from the ParentNode

Second, if they create a new nodeRelation (without deleting the existing one) and click the first one,
it jumps to the second one. The first one should be deleted OR they need a way to delete it before they create it.
Here is the code:

PostJson($"/episerverapi/commerce/nodes/{nodeRelation.ParentNodeCode}/noderelations", json);
Json = {"ChildNodeCode":"fjr_sales_Clothes_Trekking_Singi","ParentNodeCode":"fjr_sales_Clothes_Trekking","SortOrder":0}

Attachment List

N/A

Fix Version/s: EPiServer.ServiceApi 5.4.4;
Jun 09, 2020
COM-11168
  service api- PUT modifies the Created datetime of ordernotes

When sending a PUT request to /orders endpoint, the Service API discards the values in the body of request for orderNotes.Created fields and sets it to the datetime.now like value.

Fix Version/s: EPiServer.ServiceApi 5.4.4;
May 17, 2020
COM-10612
  [Service API] CMS content export service cannot export CMS content

Preconditions:

  • Install and configure the Service API
  • Quicksilver site has cms data

Steps to reproduce:

  1. Run the CMS Bulk Export method.
    episerverapi/commerce/export/site/ {siteName}

    => System returns a response.

  2. Save the response to an episerverdata file.
  3. Open the exported file.

Expected:
CMS data in the exported file.

Actual:
No CMS data in the exported file.

Fix Version/s: EPiServer.ServiceApi 5.4.3;
Mar 26, 2020
COM-10701
  Bug in Service API "episerverapi/commerce/import/upload/commit/"
Environment Information
Issue Description

The problem occurs when uploading files in chunks and then performing the commit, which attempts to merge the file chunks into a single file. The file parts seem to be processed in the wrong order.

When uploading a file in chunks, temporary files are created by Episerver with the following name pattern "startByte_endByte.split".

example:
file size: 11000 bytes
chunk size: 1000 bytes

This results in 11 split files in the episerver temp folder, named as follows.
0_1000.split
1000_2000.split
2000_3000.split
3000_4000.split
4000_5000.split
5000_6000.split
6000_7000.split
7000_8000.split
8000_9000.split
9000_10000.split
10000_11000.split

When performing the commit operation, Episerver processes them in the filename-order, resulting in a corrupted file after the merge.

The process order for this example would be (the items in red causing corrupted result):
0_1000.split
10000_11000.split
1000_2000.split

2000_3000.split
3000_4000.split
4000_5000.split
5000_6000.split
6000_7000.split
7000_8000.split
8000_9000.split
9000_10000.split

Fix Version/s: EPiServer.ServiceApi 5.4.3;
Mar 26, 2020
COM-10065
  Fix misleading properties of AddressModel in Service API

In the AddressModel, ShippingDefault and BillingDefault are easily confused with the Contact's default address.

Instead, these properties should be IsShippingAddress and IsBillingAddress to check the type of current address.

Fix Version/s: EPiServer.ServiceApi 5.4.2;
Jan 07, 2020
COM-9979
  ServiceAPI: When getting price by entry code and priceID, can return price of different entry

Precondition: Serviceapi Commerce was installed and configured for a Quicksilver site

Steps to reproduce

  1. Get Price by entry code and priceID. For example "url/episerverapi/commerce/entries/SKU-36127195/prices/1"

Expected:
Should return a 404 not found because SKU-36127195 does not have priceID = 1.

Actual:
Returns a 200 ok with priceID = 1 of different entry. Users can get all priceIDs that way.

{ "PriceValueId": 1, "CatalogEntryCode": "SKU-22153144", "MarketId": "AUS", "PriceTypeId": "AllCustomers", "PriceCode": "", "ValidFrom": "2015-04-22T11:43:10Z", "ValidUntil": "2035-04-22T11:43:10Z", "MinQuantity": 0.000000000, "UnitPrice": 6.500000000, "CurrencyCode": "AUD" }
Fix Version/s: EPiServer.ServiceApi 5.4.2;
Jan 07, 2020
COM-9980
  ServiceAPI: Cannot add organization as duplicated AddressId

Steps to reproduce

  1. Run POST /episerverapi/commerce/customers/organization/ with attached data (no AddressId)
  2. Run about request one more time without changes.

Expected:
You can post another organization with same info in step 1. (After step 1, an address is created with a random guid for AddressId.)

Actual:
After step 1, an address is created with AddressId is " (00000000-0000-0000-0000-000000000000)." So you cannot post an organization with
"ExceptionMessage": "Violation of PRIMARY KEY constraint 'PK_cls_Addr_091C2AFBD96D595D'. Cannot insert duplicate key in object 'dbo.cls_Address'. The duplicate key value is (00000000-0000-0000-0000-000000000000).\r\n The statement has been terminated.",

Fix Version/s: EPiServer.ServiceApi 5.4.2;
Jan 07, 2020
COM-10017
  ServiceAPI: Should check validation for organization ID

Steps to reproduce

  1. Get/put/delete organization by wrong GUID.

Expected:
Should return a 400 bad request error with the response body below instead of 404 not found.
{
"Message": "The request is invalid.",
"ModelState":

{ "organizationId": [ "The value '1243242' is not valid for Guid." ] }

}
Actual:
Returns a 404 not found error.

Fix Version/s: EPiServer.ServiceApi 5.4.2;
Jan 07, 2020
COM-10184
  Service API: Error when getting entry code that includes forward slash

Some Commerce Products have a forward slash in the SKU. Some customers use the product SKU as the product “Code” in the Episerver catalog. These customers cannot figure out how to access the product using the Service API if the product “Code”
includes a forward slash.
Examples:
You create a product with the Code “123”. You can retrieve the product via the Service API on the following endpoint:

GET: baseUrl/episerverapi/commerce/entries/123

However, if you change the product Code from 123 to 123/456, the following call does not work (404 error) due to the forward-slash in the URL (obviously breaking the routing):

GET: baseUrl/episerverapi/commerce/entries/123/456

One might assume that encoding the forward slash in the product Code to “%2F” would resolve the issue. For example:

GET: baseUrl/episerverapi/commerce/entries/123%2F456

But that does not work (again, a 404 not found error) is returned.

Fix Version/s: EPiServer.ServiceApi 5.4.2;
Jan 07, 2020
1 2 3 4 5 6 Next