MDVA-42806: A new company registration email is sent each time an existing company is updated via…

Categories

B2B, Web API

Components

magento/module-company

Origin

adobe-commerce-support

Since QPT

1.1.9

Issue

A new company registration email is sent each time an existing company is updated via REST API.

Steps to reproduce

1. Create a company account. 1. Use /V1​/company​/<company_id> endpoint. To update the created company, see update the company in our developer documentation. Below is a sample payload: { "company": { "id": 2, "status": 1, "company_name": "Company", "company_email": "company@example.test", "street": [ "Test" ], "city": "Test", "country_id": "US", "region_id": "1", "postcode": "12345", "telephone": "8009994301", "customer_group_id": 2, "sales_representative_id": 1, "super_user_id": 2 } }

Adobe's page lists 2.4.2 - 2.4.3-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.5.

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 MDVA-42806. On Cloud, add MDVA-42806 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its MDVA-42806/ 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 MDVA-42806
• JSON API: /api/v1/patches/MDVA-42806