Hello,
For OutSystems team,
Warning, in some versions of the outsystems UI, for example 2.15. When we use the date picker with the manually edit option active, and the date format is different from the server, we find that there are unexpected behaviors.
For example, if on the server we have the date as YYYY/MM/DD and we pass DD-MM-YYYY into the date picker, the component does not work correctly.
What is an issue if we have to work with applications that work in multiple countries (different date formats).Even after checking the flatpickr (original component) discussion forum I didn't find any fix for the behavior.
I believe it would be an added value to have these behaviors corrected in the native version of the platform, without the need to extend the date picker and add JS.
The same would be blocking the option to add letters (a regex) having this option set to true/false would be a great idea.
Hello @Mariana Junges
Thank you very much for all the detailed information you provided and also for giving visibility about the other forum posts about this. Since it was not tagged with the OutSystems UI Forge component we had no visibility under our automation (already added that association). Once I have some news I'll get back to you.
Update:- After some analysis, we found out that the underneath provider/library (flatpickr.js) used by the date and time-related pickers doesn't support this feature, so we've added this to our backlog to try to understand how feasible it is under the task code ROU-10854 but to manage expectations this is not a top priority when comparing with the team's commitments.
Cheers,GM
Could you please share an oml with the specific use case where that can be reproduced?Thank you in advance.
Hello Gonçalo,
Thank you for your response and attention. The subject had already been discussed in this forum.
Manually input DatePicker changes input date to other dateI can't share the original OML, but I replicated the behavior in this attachment.
we managed to solve the problem in our project with JS. But our project will only cover one date format at this time. But I believe that if it were necessary to use several date formats and users entered data with "unexpected" formats due to being in other locations, other tests would have to be carried out...
It's just a possibility for improvement, together with TRUE/FALSE to accept or not letters or only numbers.
The big problem here is that the date field only uses the universal "YYYY-MM-DD" format.
The best solution is to create a mask and then you can control what is done, if you keep the native html inputs.
If you don't use the mask, you have to send the setdate action to the datepicker to tell it what the new date is.
Hello, as indicated, the issue has been resolved at the project level.
Only reported to OutSystems as an opportunity for improvement.
Like input true/false for regex.
But thank you very much for your input. :)