web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Apps
Answered

onChange Date Bug

(1) ShareShare
ReportReport
Posted on by 31

Seeing and unexpected experience with the date field onChange event. I'm attempting to validate a user typed in the required 4 digit year (e.g. 2019) instead of the 2 digit abbreviation (e.g. 19) and came across this issue. On a single line of text field (SLOT) when the field loses focus (e.g. user clicks to another field) the onChange fires for that SLOT field. On the other hand, in a date field the onChange event only occurs if a user enters a valid date and when the valid date is entered it fires immediately (not when the focus changes). I setup the a test list showing some onChange experiences and the inconsistencies with the onChange event between the SLOT and the date fields.

Single Line of Text onChange:

UpdateContext({
varSLOT: DataCardValueSLOT.Text
})

Date Only onChange:

UpdateContext({
varDate: Text(DataCardValueDate.SelectedDate)
})

In action (Imgur link if embed below doesn't work):
Screen recording of bugScreen recording of bugIt'd be great if someone on the PowerApps team could chime in to confirm if this is a known bug and/or if a fix is in the works.

Categories:
I have the same question (0)
  • iDrive Profile Picture
    31 on at

    Bumping this up. Is there a dedicated bug tracker/reporting site?

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Hi @iDrive I'm sorry to see you're experiencing this issue. Your best bet would be to submit a support ticket so the Product Team can diagnose the issue and track the fixes that need to be made. 

     

    https://powerapps.microsoft.com/en-us/support/pro/

     

    @Anonymous

  • Verified answer
    iDrive Profile Picture
    31 on at

    I put in a support ticket and demonstrated the issue to the tech but was told this is "by design" but in the same breathe "we'll take this to our team for a feature enhancement." Disappointing response but wanted to close this out for any others that come across this issue.

  • billblais Profile Picture
    47 on at

    Thanks for following through on this @iDrive . I'm stymied by this as well. Agreed that is a very frustrating response (why behave differently 'by design'?), but here's hoping someone will see sense.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 392 Most Valuable Professional

#2
11manish Profile Picture

11manish 136 Super User 2026 Season 2

#3
MS.Ragavendar Profile Picture

MS.Ragavendar 109 Super User 2026 Season 2

Last 30 days Overall leaderboard