Not selected rows are deleted during mass action deletion

This article provides a patch for the known Magento Сommerce Cloud 2.2.3 issue related to having not selected records being deleted when a bulk deletion is performed in a grid in Magento Admin.

Issue

In Magento Admin, if you select customer or client records to be deleted, filter the grid, and then select the Delete action, all records are deleted. 

Steps to reproduce (with Products grid for an example):

1. Navigate to Catalog > Products in Magento Admin.
2. Select a product or multiple products.
3. Select Delete from the Actions drop-down menu.

Expected result:
Only selected products are deleted.

Actual result:
Some other products are deleted as well.

Patch

The patch is attached to this article. To download it, scroll down to the end of the article and click the file name, or click the following link:

Download MDVA-10600_EE_2.2.3_v1.composer.patch

Compatible Magento versions:

The patch was created for:

• Magento Commerce Cloud 2.2.3

The patch is also compatible (but might not solve the issue) with the following Magento versions and editions:

• Magento Commerce 2.1.8-2.1.14
• Magento Commerce 2.2.0-2.2.2, 2.2.4-2.2.5
• Magento Commerce Cloud 2.2.4-2.2.5

How to apply the patch

We strongly recommend applying and testing the patch on the Integration/Staging environment, before applying it Production. We also recommend to have a recent backup before any manipulations.

How to apply this patch for Magento Commerce Cloud

1. If you do not have a directory named m2-hotfixes in the project root, please create one.
2. Copy the MDVA-10600_EE_2.2.3_v1.composer.patch file to the m2-hotfixes directory.

3. Add, commit, and push your code changes:

   git add -A && git commit -m "Apply MDVA-10600_EE_2.2.3_v1.composer patch" && git push origin

How to apply this patch for Magento Commerce

1. Upload the patch to your Magento root directory.
2. Run the following SSH command:

   patch -p1 < MDVA-10600_EE_2.2.3_v1.composer.patch

   (If the above command does not work, try using -p2 instead of -p1)
3. For the changes to be reflected, refresh the cache in the Admin under System > Cache Management.

Useful links

Apply custom patches to Magento Commerce (Cloud)

Attached Files