Known Issues · Commerce Cloud API/OCAPI

Work Search Refinement "Sort By Category" Not Working in SFRA

Commerce Cloud API/OCAPI

When testing a new implementation of the Storefront Reference Architecture, the site does not return the expected search refinement results while using "Sort By Category" option, but will instead sort the category by alphabet. When operating correctly, expected category refinement search result should...

In Review ·Reported By 1 ·Updated 2 days ago

OCAPI Batch requests throwing client ID missing and wrong version

Commerce Cloud API/OCAPI

When sending OCAPI requests to Batch API endpoint with an expired OAuth token, there is an error response which contains a wrong version and a misleading fault type.

In Review ·Reported By 2 ·Updated 3 days ago

OCAPI - SessionBrigde - Empty Basket is lost after using session bridge

Commerce Cloud API/OCAPI

When customer applications are using OCAPI Session Bridge to switch from plain OCAPI calls to Custom Controller/Pipeline calls previously created baskets will be lost if they don't include any product line item.

In Review ·Reported By 0 ·Updated 4 days ago

System Job sfcc-site-archive-export is not exporting Meta data when called by OCAPI

Commerce Cloud API/OCAPI

Exporting only meta data doesn't work, when we run Global job(sfcc-site-archive-export) by OCAPI call. Export does not happen if you send Meta data as true in post call data. All the data is exported when we manually run the job. Request: Request:https://Instance_URL/s/-/dw/data/v19_1/jobs/sfcc-site-archive-export/executions POST...

In Review ·Reported By 0 ·Updated 5 days ago

API Explorer Not Working on Some Browsers

Commerce Cloud API/OCAPI , Commerce Cloud Platform

The API Explorer is not working on Chrome Browsers running Version 76 and Firefox Browsers with the "Modify Header Value (HTTP Headers)" extension enabled. When trying to authorize or explore, users will receive an error

In Review ·Reported By 4 ·Updated 6 days ago

DATA OCAPI GET /customer_lists/{list_id}/customers/{customer_no} is not returning the primary/default address of the customer

Commerce Cloud API/OCAPI

DATA OCAPI GET /customer_lists/{list_id}/customers/{customer_no} is not returning the primary/default address of the customer

In Review ·Reported By 1 ·Updated 6 days ago

Handshake failure when code is uploaded with Build-Suite

Commerce Cloud API/OCAPI , Commerce Cloud Platform , Commerce Cloud Admin

Customers may experience SSL Handshake failures when they upload the code using the Build-Suite Error: write EPROTO 140162281645888:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1536:SSL alert number 40

In Review ·Reported By 5 ·Updated 17 days ago

OCAPI SHOP API baskets/{basket_id}/approaching_discounts call fails with exception

Commerce Cloud API/OCAPI

OCAPI call /baskets/{basket_id}/approaching_discounts tries to return amount value even in case of discount type Bonus. In case of bonus discounts there will be no amount value present and hence it fails while checking discount type. Amount value should be returned only in case of discount type “...

Fixed in version 19.9 Preview Update & GA ·Reported By 1 ·Updated 25 days ago

Data API update inventory: when "reset_date" is older (before) the response is an internal server error 500

Commerce Cloud API/OCAPI

When working with the Data API: /inventory_lists/*/product_inventory_record/* the semantic errors occurred, are being answered with a 500 Internal Server Error only. However, is expected that the real error message will be returned.

In Review ·Reported By 2 ·Updated 2019-08-02

ScriptingException Logged Using ExportInventoryLists Pipelet

Commerce Cloud API/OCAPI , Commerce Cloud Platform

When executing the “ExportInventoryLists” Pipelet, an Error Log is thrown stating: “…TypeError: Cannot read property ‘demand ware’ from null…”

Fixed in version 19.8 Preview ·Reported By 2 ·Updated 2019-07-24

1 to 10 of 37 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.