Date fields not allowing year 2025

[Pbo]

Afternoon everyone,

As we get closer to the New Year I've noticed that my Lansweeper ticketing system is no longer allowing users to select dates past 2024. I've done some searching on Google/LS forums about a similar issue I haven't seen anything out of order. The most popular suggestion is in the link below but sadly these resolutions didn't apply.

https://community.lansweeper.com/t5/archive/release-3-5-date-format-problem/m-p/5765/page/2

Has anyone encountered this issue; or have any suggestions for a solution?

Thank you,

[FrankSc · Accepted solution]

Dear, 

This has indeed been reported by a few other users, we are looking into this.

We will fix this in the next release, which we hope to release at the beginning of January.

[Obi_1_Cinobi · Accepted solution]

Hello there!

This issue is resolved in Lansweeper version 12.2.1.6. You can update to the latest Lansweeper version by following the steps in this guide: https://www.lansweeper.com/knowledgebase/updating-your-installation/

If needed, you can always check our changelog to see all the additions, changes, and fixes that have been implemented in the Lansweeper software: https://www.lansweeper.com/changelog.aspx

The latest Lansweeper installer can be found here: https://www.lansweeper.com/update-lansweeper/
The latest LsAgent installers can be found here: https://www.lansweeper.com/download/lsagent/

[Pbo]

Thanks for keeping me updated on this issue. I'll apply this new update tonight and hope for the best.

Thanks again,

[Salva]

Hi, 

just for info:

07/01/2025 --> invalid value

7/1/2025 --> working fine

[MichaelUnify]

*HHHISSSS*

The delay reeally sucks, we use this in all forms to control all of IMACD, so significant processes as now unavailable to the business. This is a large and very visible issue to the business.

[CCMC]

Checking to see if there is a specific date when this will be released, as this is effecting us as well.

[FrankSc · Accepted solution]

Dear, 

This has indeed been reported by a few other users, we are looking into this.

We will fix this in the next release, which we hope to release at the beginning of January.