ACSD-68011: Non-existent SKUs are assigned to a shared catalog via…

Categories

B2B, Web API

Components

magento/module-shared-catalog

Origin

adobe-commerce-support

Since QPT

1.1.72

Issue

Non-existent SKUs are assigned to a shared catalog via /V1/sharedCatalog/:id/assignProducts REST API.

Steps to reproduce

Send a POST request to assign a non-existent SKU to a shared catalog using the /rest/V1/sharedCatalog/1/assignProducts endpoint. curl --location 'https://example.test/rest/V1/sharedCatalog/1/assignProducts' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer bearer_value' \ --data '{ "products": [ { "sku": "test_not_existing2" } ] }'

Adobe's page lists 2.4.7-p4 - 2.4.8-p2 (B2B 1.5.1 - 1.5.2-p2) as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 1.5.3.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACSD-68011. On Cloud, add ACSD-68011 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACSD-68011/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.

Patch files and compatible versions

Sources

• Adobe documentation for ACSD-68011
• JSON API: /api/v1/patches/ACSD-68011