cancel
Showing results for 
Search instead for 
Did you mean: 
mazenahmed
Employee
Employee
Status: New

Description:

When applying a custom datetime format mask in Analyzer (e.g., dd-MMM-YYYY HH:mm:ss), the field accepts both uppercase YYYY and lowercase yyyy without any indication that they represent different values:

  • yyyy = calendar year
  • YYYY = week-based year (ISO week-numbering year)

Near the year-end/year-start boundary, using YYYY instead of yyyy can cause a date to display in a different calendar year than the actual underlying value (e.g., a December 2025 date displaying as December 2026), with no warning or validation at the point of entry.

Request:

Add a short inline example or tooltip in the format-entry UI showing the difference between YYYY and yyyy with sample output, so users can see the effect of their chosen format before applying it. This would also be a helpful addition to the datetime format documentation, shown alongside the format field itself rather than only in a separate reference page.

Why this matters:

This isn't about adding new functionality — both formats are intentional and each serves a valid purpose depending on whether a customer needs calendar-year or week-based-year reporting. The issue is that nothing in the product surfaces this distinction at the moment someone configures the format, making it easy to select the wrong one unintentionally.