Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Filter Order in Magento -Error during Filter "Something went wrong with processing the default view and we have restored the filter to its original state" #38901

Closed
curtisgift opened this issue Jul 4, 2024 · 11 comments
Assignees
Labels
duplicate Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report.

Comments

@curtisgift
Copy link

Preconditions (*)

  1. Whenever we filter data from ORDERS an error always occurred that ""Something went wrong with processing the default view and we have restored the filter to its original state" . We cannot filter any data from ORDERS due to that error. Please fix and if possible a customer support can contact directly on our email.

Steps to reproduce (*)

Expected result (*)

  1. [Screenshots, logs or description] We should be able to extract data of Orders whenever we filter for a desired output or result in ORDERS.

Actual result (*)

  1. [Screenshots, logs or description] However, during filter in ORDERS an error occur. "Something went wrong with processing the default view and we have restored the filter to its original state"
Copy link

m2-assistant bot commented Jul 4, 2024

Hi @curtisgift. Thank you for your report.
To speed up processing of this issue, 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:


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.

Copy link

m2-assistant bot commented Jul 4, 2024

Hi @engcom-Bravo. 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).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Jul 4, 2024
@engcom-Bravo
Copy link
Contributor

Hi @curtisgift,

Thanks for your reporting and collaboration.

we have verified the issue in Latest 2.4-develop and we are not able to reproduce the issue.We are able to filter the orders.

Could you please refer this comment #26515 (comment) it may resolves the issue and check the issue in Magento 2.4-develop instance.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Jul 4, 2024
@curtisgift
Copy link
Author

curtisgift commented Jul 4, 2024 via email

@engcom-Bravo
Copy link
Contributor

Hi @curtisgift,

Thanks for your update.

FYI.. Sometimes, this error can occur due to version upgrade. Check "catalog_product_entity" table in DB and verify if any Products have NULL as SKU value
Run > SELECT * FROM catalog_product_entity WHERE sku IS NULL to check all product not have sku NULL, then update them.
Another temporary fix is to clear "ui_bookmark table". > TRUNCATE ui_bookmark;
Also make sure to clear cache and add necessary permission/rights.

Kindly recheck the issue on Magento 2.4-develop branch as it has the latest code base and provide missing steps to reproduce if you are still facing the issue.

Thank you

@curtisgift
Copy link
Author

curtisgift commented Jul 5, 2024 via email

@engcom-Bravo
Copy link
Contributor

Hi @curtisgift,

Thanks for your update.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Screenshot 2024-07-08 at 13 34 09

Kindly check if any third party modules causing the issue.

Thanks.

@atIOCrON
Copy link

atIOCrON commented Jul 9, 2024

We have the same issue since upgrading to v2.4.7-p1.

@atIOCrON
Copy link

For anyone else looking for a fix, please see here:

#38916

@engcom-Bravo
Copy link
Contributor

@atIOCrON Thanks for your Contribution!!.

Hi @curtisgift,

Could you please refer this #38901 (comment) and we are closing this duplicate for this #38916.

Thanks.

@hclauss-ltk
Copy link

Hello everyone,

we have the same problem. We can´t filter our products anymore and because of the error we also can´t see the product overview in general. Are there any news on how to reset it?

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

4 participants