Ui component grid filter not working

[toantvlf]

Preconditions and environment

• Magento version 2.4.4

Steps to reproduce

1, Attribute Product Name Set Values Required = NO
2, Create New Attribute Set same Attribute Set Default
3, Import product with new attribute set (
catalog_product.csv
)
4,Go to Catalog > Product Grids-> Filter with new attribute set or SKU of new product

Expected result

Grid should be filtered by attribute set or SKU

Actual result

You will see that grid not filter and show error.

and in file system.log

Additional information

I can't save new product with product name empty (attribute product name not required

)

Release note

No response

Triage and priority

• 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 @toantvlf. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• 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, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.

[engcom-Delta]

Hi @toantvlf ,
Thank you for reporting and collaboration. Verified the issue on Magento 2.4-develop branch but could not able to reproduce the issue.Can you please check on 2.4-develop branch whether you are still able to reproduce the issue.

Please refer the screenshots.

Steps followed:

1.Set Values = No

2. New Attribute set - Test Attribute

3. Imported New Attribute Set
   catalog_product (3).csv

4 . Filtered with New Attribute Set

Regards,

[toantvlf]

please set product name empty when import product

[engcom-Hotel]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Hotel, here is your Magento Instance: https://5c114e49a7aa25798af968715ab63c95.instances.magento-community.engineering
Admin access: https://5c114e49a7aa25798af968715ab63c95.instances.magento-community.engineering/admin_1d6d
Login: 14050def
Password: 49a6a626d0a1

[engcom-Delta]

Hi @toantvlf ,
Verified the issue but could not able to reproduce the issue.Can you please check on 2.4-develop branch whether you are still able to reproduce the issue.please refer the screenshots.


Test Dev.csv

[toantvlf]

Hi @toantvlf , Verified the issue but could not able to reproduce the issue.Can you please check on 2.4-develop branch whether you are still able to reproduce the issue.please refer the screenshots. Test Dev.csv

in screenshot grid product of you - product still has the name but in file csv name is empty - did you import properly?

I checked the code, same issue, because you not check isset for $item['name']

[engcom-Hotel]

@magento give me 2.4-develop instance

[magento-deployment-service]

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