Attribute is returned as aggregation in products query even if Use in Search Results Layered Navigation is set to no

[t-heuser]

Preconditions (*)

1. Magento 2.4.2

Steps to reproduce (*)

1. On any attribute set the setting "Use in Search Results Layered Navigation" to no (using price as example here)
2. Execute the following graphql query:

query searchProducts {
    products(search: "") {
        aggregations {
            label
        }
    }
}

Expected result (*)

Actual result (*)

Whats the problem about it (*)

The huge problem is here that if you build filters based on the aggregation field the user will be able to filter the price. But if you try to filter via the price if it's disabled for layered navigation you'll receive the following error:

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @oneserv-heuser. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[t-heuser]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @oneserv-heuser. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @oneserv-heuser, here is your Magento Instance: https://b21cb62d5a70b1ae6f2ad997506f84a3-2-4-develop.instances.magento-community.engineering
Admin access: https://b21cb62d5a70b1ae6f2ad997506f84a3-2-4-develop.instances.magento-community.engineering/admin_e715
Login: c5eec167
Password: 38052939e259

[t-heuser]

@magento I can confirm that this issue is reproducible on the vanilla magento instance

[t-heuser]

I just found out that this issue not only exists for the price attribute but for all attributes. Magento ignores the settings in the backend. If you set the setting "Use in Search Results Layered Navigation" to false then the attribute gets returned when asking for the aggregation field but you cannot use it in the field ProdutAttributeFilterInput.

[khrystynastolbova]

@magento I am working on this

[khrystynastolbova]

Hi @oneserv-heuser.
I tested, and Magento really ignores the settings in the backend of the "price" field, but I have no problems with other attributes.

The settings for the "price", "visibility", "category_ids" fields are specifically ignored (in file CatalogGraphQl/Plugin/Search/Request/ConfigReader.php)

/**
     * Generate search request for search products via GraphQL
     *
     * @return array
     * @SuppressWarnings(PHPMD.CyclomaticComplexity)
     */
    private function generateRequest()
    {
        $request = [];
        foreach ($this->getSearchableAttributes() as $attribute) {
            if (\in_array($attribute->getAttributeCode(), ['price', 'visibility', 'category_ids'])) {
                //some fields have special semantics
                continue;
            }
           ...

The price is added separately in the file CatalogGraphQl/etc/graphql/di.xml

    <type name="Magento\CatalogGraphQl\DataProvider\Product\LayeredNavigation\LayerBuilder">
        <arguments>
            <argument name="builders" xsi:type="array">
                <item name="price_bucket" xsi:type="object">Magento\CatalogGraphQl\DataProvider\Product\LayeredNavigation\Builder\Price</item>
                <item name="category_bucket" xsi:type="object">Magento\CatalogGraphQl\DataProvider\Product\LayeredNavigation\Builder\Category</item>
                <item name="attribute_bucket" xsi:type="object">Magento\CatalogGraphQl\DataProvider\Product\LayeredNavigation\Builder\Attribute</item>
            </argument>
        </arguments>
    </type>

[t-heuser]

@khrystynastolbova You're right, it only affects those attributes. I tried it again and my custom attributes are not returned. Maybe that was something cache related back then.