[OutSystems UI] Undocumented behaviour for DatePicker and initial nulldate

Forge Component
Published on 25 Aug by OutSystems R&D
91 votes
Published on 25 Aug by OutSystems R&D


There seems to be an undocumented (hardcoded) limit on selecting dates with OutSystemsUI Web DatePicker widget. I cannot select a date that's more than 100 years off from initial date with default properties.

I'm aware there are MinDate and MaxDate properties for the widget, but as platform does not have convenient Datetime.MaxValue / Datetime.MinValue functionalities exposed, I feel it's stupid to have the default configuration / settings with this widget to be set like this.

I have a use case where I need to initialize date with platform null value (or, every occasion where date value is not provided).

Steps to reproduce:

  1. initialize datepicker with null date
  2. open datepicker, click today
  3. "today" is 100yrs from initial date
  4. dates after initial + 100yrs are not selectable

This can be demonstrated also in OutSystemsUI widget demo page (  https://outsystemsui.outsystems.com/OutSystemsUIWebsite/PatternDetail?PatternId=31) - try to select a date more than 100 yrs in the past or in the future.

Yes, I can set the properties with something silly like:

DateTimeToDate(AddYears(NullDate(),120)) | DateTimeToDate(AddYears(CurrDate(),120))

...but this seems very counter-intuitive.