After overriding the core sales_order_grid.xml present under Magento_Sales, While Accessing Orders Via Magento Admin, Getting the error

[rishibankaradicle]

Preconditions and environment

• Magento version :- 2.4.7-p5

• Anything else that would help a developer reproduce the bug

I have recently create an .xml file under the view/adminhtml/ui_component directory to override the functionality of core sales_order_grid.xml file to add the time as well along with the created_at filter.

After running all the deployment commands, when trying to access the sales > orders via admin, getting the below error:-

TypeError: Magento\Framework\View\Element\UiComponentFactory::argumentsResolver(): Argument #2 ($componentData) must be of type array, null given, called in /var/www/ocl/ecommerce/vendor/magento/framework/View/Element/UiComponentFactory.php on line 235 and defined in /var/www/ocl/ecommerce/vendor/magento/framework/View/Element/UiComponentFactory.php:183

I am implementing solution based on article here: https://stackoverflow.com/questions/47994925/magento-2-how-to-show-date-time-filter-in-sales-order-grid

Steps to reproduce

1. Login to Magento admin portal.
2. Go to Sales > Order.
3. Apply filter on created_at.

Expected result

Orders placed between the applied filter dates should only show.

Actual result

Upon going to sales > orders, getting the below error:

TypeError: Magento\Framework\View\Element\UiComponentFactory::argumentsResolver(): Argument #2 ($componentData) must be of type array, null given, called in /var/www/ocl/ecommerce/vendor/magento/framework/View/Element/UiComponentFactory.php on line 235 and defined in /var/www/ocl/ecommerce/vendor/magento/framework/View/Element/UiComponentFactory.php:183

Additional information

No response

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

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

[rishibankaradicle]

@engcom-Bravo Did you get a chance to take a look into this?

[rishibankaradicle]

@engcom-Bravo Is there any update on the issue?

[rishibankaradicle]

@magento Is there anyone looking into this?

[m2-assistant]

Hi @engcom-Hotel. 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

  - 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-Hotel]

Hello @rishibankaradicle,

Thanks for the report!

We are using this board to post the bugs/issues in Magento 2/Adobe Commerce library. But after reading the above issue description, it seems that there is some configuration issue.

I suggest you to post your query in Magento Community, you might get reply.

Please let us know if we missed anything, meanwhile we are closing this issue.

Thanks

[rishibankaradicle]

@engcom-Hotel @engcom-Bravo I have posted the question here as suggested:-

https://magento.stackexchange.com/q/376894/123946