cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
iDrive
Advocate I
Advocate I

onChange Date Bug

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.

1 ACCEPTED SOLUTION

Accepted Solutions

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.

View solution in original post

4 REPLIES 4
iDrive
Advocate I
Advocate I

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

Anonymous
Not applicable

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

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.

View solution in original post

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.

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Carousel April Dunnam Updated 768x460.jpg

Urdu Hindi D365 Bootcamp

Dont miss our very own April Dunnam’s The Developer Guide to the Galaxy! Find out what the Power Platform has to offer for the traditional developer.

Top Solution Authors
Top Kudoed Authors
Users online (2,063)