UPSTREAM FIX

magento2-40419: Store-scoped decimal attributes returning default values with price

Community fix magento2-40419 merged into magento/magento2 on 2026-05-20, not in a release yet; applies cleanly to 34 releases from 2.4.6 to 2.4.9.

Fixes store-scoped decimal attributes returning default values with price edited

Pull request title: Unable to get product collection scoped `decimal` attribute if price is globally scoped
Pull request: magento/magento2#40419
Issues: #40218 human
Author: @KrasnoshchokBohdan
Merged: 2026-05-20
Fixed in: no release yet
Reported on: 2.4.8-p2
Categories: Catalog/Product
Components: magento/module-catalog

Labels

Area: Catalog
Component: Attributes
Priority: P3
Severity: —
Reported on (labels): 2.4.8-p2

Issue

Title and steps come from the upstream issue and pull request.

Description

Loaded products in collection does not have example*decimal*attr values. If we remove price from collection attributes select, then it works as expected.
This works:

$collection->setStoreId(1);
$collection->addAttributeToSelect('example*decimal*attr');
$collection->load();

Adding $collection->addAttributeToSelect('price'); before loading collection, causes bug, that example*decimal*attr values are not present.

Steps to reproduce

Problem is pretty straightforward.
1. Set price as global (it's by default)
1. Add decimal scoped attribute example*decimal*attr
1. Set decimal attribute value on some products on store scope (not global - store_id > 0)
1. Create product collection for scope where created attribute have value (i.e. store_id = 1)
1. Add attributes to select:

$collection->setStoreId(1);
$collection->addAttributeToSelect('example*decimal*attr');
$collection->addAttributeToSelect('price');
$collection->load();

Expected result

Loaded products in collection have example*decimal*attr values.

Actual result

Loaded products in collection does not have example*decimal*attr values. If we remove price from collection attributes select, then it works as expected.
This works:

$collection->setStoreId(1);
$collection->addAttributeToSelect('example*decimal*attr');
$collection->load();

Adding $collection->addAttributeToSelect('price'); before loading collection, causes bug, that example*decimal*attr values are not present.

Taken from the upstream issue.

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

Line	Code match per tag	Tests
2.4.6	2.4.6 clean 2.4.6-p1 clean 2.4.6-p2 clean 2.4.6-p3 clean 2.4.6-p4 clean 2.4.6-p5 clean 2.4.6-p6 clean 2.4.6-p7 clean 2.4.6-p8 clean 2.4.6-p9 clean 2.4.6-p10 clean 2.4.6-p11 clean 2.4.6-p12 clean 2.4.6-p13 clean 2.4.6-p14 clean 2.4.6-p15 clean	2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7	2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean	2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: fails before, passes afterintegration: fails before, passes after
2.4.8	2.4.8 clean 2.4.8-p1 clean 2.4.8-p2 clean 2.4.8-p3 clean 2.4.8-p4 clean 2.4.8-p5 clean	2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: fails before, passes afterintegration: fails before, passes after
2.4.9	2.4.9 clean	2.4.9: fails before, passes afterintegration: fails before, passes after

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 98.0%. Probability it is security relevant: 0.8%.

Show the model's answers and probabilities

Question	Answer	Probabilities	Confidence
Change kind	bugfix	bugfix 96.0%, refactor 1.7%, tests_only 0.9%, feature 0.6%, dependency 0.4%, docs_only 0.3%	90.7%
Area	catalog	catalog 93.7%, admin 1.4%, framework 1.2%	86.2%
Reported version	2.4.8-p2	2.4.8-p2 62.7%, 2.4.8-p3 2.0%, 2.4.8 1.6%	38.9%
Scope	0.85 of 2	1 43.3%, 0 35.9%, 2 20.8%	3.9%
Risk	0.90 of 2	0 38.7%, 1 32.0%, 2 29.2%	0.7%
Worth backporting	1.60 of 2	2 66.7%, 1 26.4%, 0 7.0%	27.8%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-40419/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Bundle README (what the ZIP ships)

# magento2-40419

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/40419
Issue: https://github.com/magento/magento2/issues/40218
Author: @KrasnoshchokBohdan
Source commit: 188c920a44a032d83484b125f3d69d7e0841d1d2
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.