# Date formatting in vision must occur through the Swing utilities **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition81\ **Created:** [June 19, 2024, 5:01pm UTC](https://forum.inductiveautomation.com/t/date-formatting-in-vision-must-occur-through-the-swing-utilities/92109 "2024-06-19T17:01:10Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [June 19, 2024, 5:07pm UTC](https://forum.inductiveautomation.com/t/date-formatting-in-vision-must-occur-through-the-swing-utilities/92109/2 "2024-06-19T17:07:02Z")
The change in question has already been reverted ([Nightly 8.1 Changelogs - 2024 - #82 by system](https://forum.inductiveautomation.com/t/nightly-8-1-changelogs-2024/83608/82); n.b. 8.1.41 was changed to a hotfix release so the changes mentioned will be live in 8.1.42), but it was unlikely to (deliberately) affect you anyways. The warning was only _intended_ to show up if you accessed the date formatter inside certain Vision components (e.g. popup calendar) from an asynchronous thread. All scripting in Vision is automatically on the EDT unless you explicitly invoke an asynchronous thread, so it's very unlikely you would even have noticed _that_ aspect. However, **our** code turns out to very much access these components on asynchronous threads (e.g. in find and replace, or during template repeater construction) so we reverted the change anyways, because it's impossible to distinguish between those different cases. I would definitely recommend postponing your upgrade until 8.1.42 is available to avoid the nuisance warnings in the designer, though. --- _[View the full topic](https://forum.inductiveautomation.com/t/date-formatting-in-vision-must-occur-through-the-swing-utilities/92109)._