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
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Top Solution Authors
Top Kudoed Authors
Users online (3,000)