Salesforce Known Issues

Known Issues · Commerce Cloud API/OCAPI

OCAPI ShopAPI product_search request with 4 or more refine parameter htype returns incorrect ProductSearchRefinement

Commerce Cloud API/OCAPI , Commerce Cloud Platform , B2C Commerce 20.1

When the shop api call has more than 3 values for htype param, the ProductSearchRefinement values are missing in the response.

In Review ·Reported By 2 ·Updated Today

dw.order.ShippingOrder.createShippingOrderItem API is slow when dealing with orders containing around or above 100 products line items

Commerce Cloud API/OCAPI

When dw.order.ShippingOrder.createShippingOrderItem() deals with orders containing around or above 100 products line items (this happens often, as the sites are B2B storefronts), the execution time of API execution is increasingly slow, up to a point that it’s not acceptable. Some tests show that...

Fixed in version 20.2 Preview ·Reported By 3 ·Updated 3 days ago

Inventory Data API returns wrong turnover value

Commerce Cloud API/OCAPI

The following ocapi call returns wrong information for the "InventoryTurnover"-value in case of a previously run allocation reset: resource called returning faulty value: value...

Fixed in version 20.2 Preview ·Reported By 1 ·Updated 3 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 9 ·Updated 4 days ago

Some Instances of CSRF Validation in SFRA Not Working/Showing Mismatch Error

Commerce Cloud API/OCAPI , Commerce Cloud Platform

In SFRA, the csrfProtection.validateAjaxRequest method can be used to perform CSRF validation. In some versions of SFRA, this call is made via a GET request vs. a POST request (ex: Cart-AddCoupon). When this happens, while intermittent, the validation may succeed (regardless if the tokens match) or users...

In Review ·Reported By 3 ·Updated 6 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.

Fixed in version 20.1 Preview ·Reported By 2 ·Updated 6 days ago

ADHOC Coupon Line Items Created Wrongfully Marked Invalid Due To Incorrect Status.

Commerce Cloud API/OCAPI

When utilizing the createCouponLineItem(couponCode : String) method of the LineItemCtnr class, the corresponding couponlineitem object is created without an associated campaign or promotion. This coupon is wrongfully marked as UNKNOWN as opposed to ADHOC. Because this coupon is marked as unknown, the...

Fixed in version 20.1 Preview ·Reported By 1 ·Updated 6 days ago

Lock contention in com.demandware.core.transport.schema.CompositiveVersionInfo.floor

Commerce Cloud API/OCAPI

We observed performance degradation at the App tier due to significant lock contention in com.demandware.core.transport.schema.CompositiveVersionInfo.floor with OCAPI caching disabled. Timeout were noticed for dw_coupon service and product_search OCAPI calls. The following (or similar) messages are...

In Review ·Reported By 1 ·Updated 6 days ago

For OCAPI "product_search" resource request, search refinement string value having a comma computes search filter incorrectly

Commerce Cloud API/OCAPI

For OCAPI "product_search" request, if the search refinement string value in the request has a comma, the search filter is computed incorrectly and response returns no products as search results.

Fixed in version 20.1 Preview ·Reported By 1 ·Updated 6 days ago

Error When Setting Quantity to Less Than 1 on SFRA

Commerce Cloud API/OCAPI

When setting a Product's quantity to a fractional value less than 1, an error is thrown and the action is not completed

In Review ·Reported By 2 ·Updated 7 days ago

1 to 10 of 49 | 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.