Fixed #32983 Datetime custom attribute throws exception at mass attribute updates from admin product grid

[Rakhi161]

Preconditions (*)
1.Magento version 2.4.1

Steps to reproduce (*)
Create a custom date and time attribute and assign it to an attribute set.
From admin panel go to Catalog -> Products -> Select a product which is assigned to the attribute set which includes the newely created date and time custom attribute -> Actions -> Update attributes

Expected result (*)

Actual result (*)

Resolved issues:

1. resolves [Issue] Fixed #32983 Datetime custom attribute throws exception at mass attribute updates from admin product grid  #33034: Fixed Datetime custom attribute throws exception at mass attribute updates from admin product grid #32983 Datetime custom attribute throws exception at mass attribute updates from admin product grid

[m2-assistant]

Hi @Rakhi161. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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

[mrtuvn]

If this is your first contribution can you sign CLA ?
Also if possible please cover changes with some kind of automation tests

[gabrieldagama]

@magento create issue