This section describes known issues in the Oracle Commerce Cloud REST APIs.

26866153 “Nr” parameter no longer present in the Search Results and Navigation pages

Default queries to the Navigation and Search Result pages no longer contain the Nr parameter in the URL. The Nr parameter is still supported; however, due to performance optimizations, the default price group filter contained in this parameter is no longer required.

Workaround: Custom integration code that relies on the Nr parameter being returned should be tested to ensure this continues to function correctly.

25768491 Change to error code when setting defaultLocaleId of a site object to null

In versions of Oracle Commerce Cloud prior to 17.2, using the updateSite endpoint in the Admin API to set the defaultLocaleId property of a site object to null resulted in the following error:

{
  "errorCode" : "27000",
  "message" : "Failed to get the locale with ID null",
  "status" : "500"
}

In version 17.2 and above, the following error results instead:

{
  "errorCode" : "30003",
  "message" : "Missing required property: defaultLocaleId",
  "status" : "400"
}

25839951 Requests from Postman HTTP client on Chrome browser fail

If you issue API calls using the Postman HTTP client that runs in the Google Chrome browser, you may receive 403 (Forbidden) errors. These errors are due to Postman including an Origin header that is rejected by Commerce Cloud.

Workaround: There are several workarounds available, including configuring Commerce Cloud to accept the default Origin header, using Postman Interceptor to explicitly set the Origin header to a different value, or using the Postman native application (which does not send an Origin header). For more information, see the following support document:

https://support.oracle.com/rs?type=doc&id=2245936.1

26567677 Audience rules don’t work for Shopper Type and B2C users where profileType=null

The Shopper Type property is not available in this release. If you are an account-based customer, and created an audience that used the Shopper Type property in a rule prior to 17.4, when you upgrade to this release and open the audience in the Audiences interface, the rule will return an error.

Workaround: Open the audience in the Audiences interface and remove Shopper Type property or the rule containing the Shopper Type property.