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"

[curtisgift]

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"

[m2-assistant]

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:

• @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.

[m2-assistant]

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]

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.

[curtisgift]

Sir, We tried to filter it just now and this is the error occurred, same as previous. [cid:158fb571-ba97-48a1-9ebd-772ddee71756] Thank you Regards Curtis Mar [all-logo-all-office] Unit 2202, 22/F, Causeway Bay Plaza 1, 489 Hennessy Rd, Causeway Bay, Hong Kong. Unit 2403, 24/F, Tsuen Wan Ind Centre, 220 Texaco Rd, Tsuen Wan, Hong Kong. 21 Ubi Rd 1, #3-01, Singapore 408724. 8 Jalan Tun Sambanthan 3, Brickfields, 50470, Kuala Lumpur, Malaysia. T + 852 2730 0885<tel:%2B%20852%202730%200885> │ F + 852 2730 0206<tel:%2B%20852%202730%200206> giftflowers.com.hk<http://giftflowers.com.hk/> │gifthampers.com.hk<http://gifthampers.com.hk/> │giftsomething.com<http://www.giftsomething.com/> [https://mail.google.com/mail/u/2?ui=2&ik=14cf2c4d59&attid=0.0.3&permmsgid=msg-f:1750271285094013205&th=184a3675e0985915&view=fimg&fur=ip&sz=s0-l75-ft&attbid=ANGjdJ9uuIorrIybMzxJ_DzYlw1BCsxcJ0eSwjeT9Oczu9lVbDRM44_zdaENvVKQda4aJHKwspMMp3-s4OHynIW1W7Urz-olwCggi3WAE9juWePJDQm34oUTI4BJfQk&disp=emb]

…

________________________________ From: Venkata Kumar Kuntumalla ***@***.***> Sent: Thursday, July 4, 2024 12:22 PM To: magento/magento2 ***@***.***> Cc: Curtis Ma ***@***.***>; Mention ***@***.***> Subject: Re: [magento/magento2] 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" (Issue #38901) Hi @curtisgift<https://github.com/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)<#26515 (comment)> it may resolves the issue and check the issue in Magento 2.4-develop instance. Thanks. — Reply to this email directly, view it on GitHub<#38901 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJUUPGZKRCAONXAPOIP2WEDZKTEXLAVCNFSM6AAAAABKKVXQUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYGA4TENZWHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[engcom-Bravo]

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]

Hi! As an update this morning. The problem left is when we filter ORDERS in PURCHASE DATE, same error still occur. But when filtering other data it is now working. Please see screenshot below [cid:b0733c5e-ae15-44a0-9925-11f3cdc31d6e] I would like to ask for extra help to fix this error since I am not familiar with technical issue or command in Magento. Thank you Regards Curtis Mar [all-logo-all-office] Unit 2202, 22/F, Causeway Bay Plaza 1, 489 Hennessy Rd, Causeway Bay, Hong Kong. Unit 2403, 24/F, Tsuen Wan Ind Centre, 220 Texaco Rd, Tsuen Wan, Hong Kong. 21 Ubi Rd 1, #3-01, Singapore 408724. 8 Jalan Tun Sambanthan 3, Brickfields, 50470, Kuala Lumpur, Malaysia. T + 852 2730 0885<tel:%2B%20852%202730%200885> │ F + 852 2730 0206<tel:%2B%20852%202730%200206> giftflowers.com.hk<http://giftflowers.com.hk/> │gifthampers.com.hk<http://gifthampers.com.hk/> │giftsomething.com<http://www.giftsomething.com/> [https://mail.google.com/mail/u/2?ui=2&ik=14cf2c4d59&attid=0.0.3&permmsgid=msg-f:1750271285094013205&th=184a3675e0985915&view=fimg&fur=ip&sz=s0-l75-ft&attbid=ANGjdJ9uuIorrIybMzxJ_DzYlw1BCsxcJ0eSwjeT9Oczu9lVbDRM44_zdaENvVKQda4aJHKwspMMp3-s4OHynIW1W7Urz-olwCggi3WAE9juWePJDQm34oUTI4BJfQk&disp=emb]

…

________________________________ From: Venkata Kumar Kuntumalla ***@***.***> Sent: Thursday, July 4, 2024 7:11 PM To: magento/magento2 ***@***.***> Cc: Curtis Ma ***@***.***>; Mention ***@***.***> Subject: Re: [magento/magento2] 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" (Issue #38901) Hi @curtisgift<https://github.com/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 — Reply to this email directly, view it on GitHub<#38901 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BJUUPGYPQ3LWVF57O72RSRTZKUUWLAVCNFSM6AAAAABKKVXQUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYG4YTCMBZHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[engcom-Bravo]

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.

Kindly check if any third party modules causing the issue.

Thanks.

[atIOCrON]

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

[atIOCrON]

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

#38916

[engcom-Bravo]

@atIOCrON Thanks for your Contribution!!.

Hi @curtisgift,

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

Thanks.