QUALITY PATCH

ACSD-47027: The slow query B2B CompanyRole GraphQL update does not work as expected

The slow query B2B CompanyRole GraphQL update does not work as expected. Quality patch ACSD-47027 for magento/module-company-graph-ql applies to Magento Open Source and Adobe Commerce 2.4.2 to 2.4.5-p17.

Categories: GraphQL, B2B
Components: magento/module-company-graph-ql
Origin: adobe-commerce-support
Since QPT: 1.1.23

Issue

The slow query B2B CompanyRole GraphQL update does not work as expected.

Steps to reproduce

1. In the Adobe Commerce Admin, go to Stores > Settings > Configurations > B2B Features and set Enable Company to _Yes_. 1. Go to the frontend and create a company. 1. After you log in as a company user, go to My Account > Roles and Permissions and add a new role. 1. Enable dev query log using bin/magento dev:que:enab. 1. Now send the below GraphQL request (id is the base64 encoded role id): mutation { updateCompanyRole( input: { id: "Mg==" permissions: [ "Magento_Company::view" "Magento_Company::view_account" "Magento_Company::user_management" "Magento_Company::roles_view" ] } ) { role { id name permissions { id text children { id text children { id text } } } } } } 1. Check the query log. 1. You can see that the above query is executed. This query is executed in app/code/Magento/CompanyGraphQl/Model/Company/Role/ValidateRole.php::validateResources.

Adobe's page lists 2.4.2 - 2.4.5-p1 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 2.4.6.

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-47027. On Cloud, add ACSD-47027 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-47027/ 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.