Wrong price indexed for configurable/composite products

[ilnytskyi]

Preconditions (*)

magento 2.3

Steps to reproduce (*)

1. Edit price or special_price on configurable product from mass action grid or saving attribute via resource model $this->productResource->saveAttribute($product, 'price'); or
   $this->productResource->saveAttribute($product, 'special_price');
2. Run reindex from cron (mb. CLI reindex as well)
3. See the price from attributes appeared on product grid
4. See the price from attributes in columns price and final_price in the table catalog_product_index_price
5. Then save configurable product from admin edit page
6. See null value saved for price attribute in catalog_product_entity_decimal
7. Wait for price reindex from cron (mb. CLI reindex as well)
8. Repeat step 4 and see 0 saved in columns price and final_price for edited configurable product

to find prices saved for configurable product use this SQL

SELECT decimal2.*
FROM catalog_product_entity
       inner join catalog_product_entity_decimal decimal2 on catalog_product_entity.entity_id = decimal2.entity_id and
                                                             attribute_id in (SELECT attribute_id
                                                                              from eav_attribute
                                                                              where attribute_code in
                                                                                    ('price', 'special_price'))
where type_id = 'configurable';

Expected result (*)

1. Price never saved for a configurable product in catalog_product_entity_decimal table from any save point e.g. resource model, repository
2. Price indexed correctly in catalog_product_index_price (data for composite products should be calculated based on child products) e.g. final_price = min_price, price = max_price attribute values from catalog_product_entity_decimal should be ignored

Actual result (*)

1. Still possible to save price and special_price for configurable/composite product in catalog_product_entity_decimal table
2. Wrong calculation of columns price and final_price in the catalog_product_index_price table

[m2-assistant]

Hi @ilnytskyi. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@ilnytskyi do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @webkul-ratnesh. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.