Differences in Available Properties Using SCIM Filter Between Admin and Storefront (Doc ID 2647088.1)

Last updated on DECEMBER 01, 2023

Applies to:

Goal

You may notice differences in the payload responses, as well as the available properties you can filter on between similar/same endpoints that are available on both Admin and Storefront rest API.

For the most part this is intended, as these are two different applications and the data made available to each will be different as well. You need to approach each instance you encounter such differences as a separate issue that needs to be discussed. Some of these differences are obviously intended, and documented.

Example:

A good example would be the /products endpoint, and specifically the available properties you can filter using SCIM with that endpoint. Notice, the childSku.id is simply not available at the storefront endpoint, but is available at the same corresponding endpoint in admin. This is not a bug, but there are changes we can make to the application in some circumstances to adjust this behavior (See below)

Admin API:

https://xxyy.com/ccadminui/v1/products?fields=repositoryId&q=childSKUs.id co "TEST"

        - This will return the expected results, the products that match the given childsku.id you are sending

Storefront API:

https://xxyy.com/ccstoreui/v1/products?fields=repositoryId&q=childSKUs.id co "TEST"

        - This will result in an error, because this field (Childsku.id) is not available to filter on using SCIM on this endpoint.

        - {errorCode: "85003", message: "Invalid attribute in query: childSKUs.id", status: "400"}

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.