Today AS-IS: Set at server level, date and time are server based. Only one format aviable today.
Suggestion to support:
The YYYY-MM-DD format, defined by ISO 8601, is the most common date format in technical systems, databases, and for international communication due to its unambiguous, chronological sorting, and compatibility across software and operating systems. While other formats like DD/MM/YYYY or MM/DD/YYYY are prevalent in specific regions, YYYY-MM-DD is the global standard for systems requiring accuracy and easy processing.
Why YYYY-MM-DD is the system standard:
Unambiguous: This format eliminates confusion between month and day, which can occur with formats like MM/DD/YYYY or DD/MM/YYYY.
Chronological Sorting: Dates written in YYYY-MM-DD format will sort correctly alphabetically, which is crucial for file management and database operations.
System Compatibility: Most software and operating systems are designed to parse and handle dates in this format easily out of the box.
International Standard: ISO 8601 is an internationally recognized standard for date and time notation, making YYYY-MM-DD essential for global communication.
Examples of common formats:
ISO 8601 (YYYY-MM-DD): 2025-10-08 (October 8, 2025)
Day-Month-Year (DD/MM/YYYY): 08/10/2025 (October 8, 2025)
Month-Day-Year (MM/DD/YYYY): 10/08/2025 (October 8, 2025)
|
Practical use of functionality?
Makes it possible to choose from more standards that support multiple countries' standards. |
|
|
What is the impact of not doing this?
Has date formatting that confuses users. |
Hi @Guest ,
I think this idea overlaps with this existing idea here: https://bcde.ideas.aha.io/ideas/BCDECORE-I-1132
Well consider these two ideas together when evaluating priorities.
Thanks, Paul.