Modern Date Picker bugged: Shows a wrong date in displaymode.view when SelectedDate returns blank

(3) Share

Report

Posted on by DamonJay

I have several modern date pickers on a screen. Each date picker is supposed to display a corresponding date field from a record when controls are in view mode, and allow for updates when they are in edit mode. The record is a global variable set by selecting a gallery item on another screen.

Everything works as expected if the date fields in the data source / record variable are all populated with a date. However, when a record with any blank date field is loaded, the corresponding modern date picker does not show as blank when in view mode. Instead, it displays the last date that was in that field, either from the previous record or one which had been selected manually prior to the control being reset.

In edit mode, the date picker correctly shows as blank, awaiting input. The correct blank value is also returned in the fx bar when viewing the SelectedDate property.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

venturemavenwill 1,198 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Yes, I have also noticed that modern date picker caches the selected date. What I usually do is explicitly define the DefaultDate property to display Blank() if the corresponding field is blank.

You can also try to reset all the date pickers when you select a record.

Was this reply helpful? Yes No
DamonJay 35 on at

Like (0)

Report
Copy link

Link copied!
Thanks for your suggestion. However, I'm not seeing a DefaultDate property in the modern date picker.

I've already tried an explicit condition in the SelectedDate property similar to below, to no effect. Have you taken a different approach that forces through the blank value in DisplayMode.View?

If(IsBlank(variablename.datefield),Blank(),variablename.datefield)

Resetting the control makes no difference to what is shown in DisplayMode.View if the underlying record field is blank. The modern date picker still holds on to the cached date value, even when the record variable is cleared and the control is repeatedly reset.

Was this reply helpful? Yes No
stephenbrownproduct 13 on at

Like (0)

Report
Copy link

Link copied!

Confirming this is still an issue in the modern date picker control. Null/empty inputs is Testing 101. It's scary how many bugs are in "GA" features.

Was this reply helpful? Yes No
ronaldwalcott 3,906 Moderator on at

Like (0)

Report
Copy link

Link copied!

I thought that you are expected to set a default date when using the control because what is considered an empty date

Was this reply helpful? Yes No
DamonJay 35 on at

Like (0)

Report
Copy link

Link copied!

@ronaldwalcott It's a perfectly common use case for any non-required field to be able to display as blank when viewing an existing record from a data table.

For example, let's say we have a screen to display the start date and end date of a task. The user loads a record for a task that has started but has not yet ended, so the end date field in our data set is empty. As such, the end date control in our app should be blank.

There is no default date applicable and the control simply will not default to blank, nor reset to a blank/empty state through normal methods. Instead, the user would see the end date from the last record displayed which did have a stored value (or else the last date manually selected using that date picker control) instead of the blank field.

It's simply not fit for purpose.

Was this reply helpful? Yes No