Incorrect dates not being corrected

[LeoC2]

In Pan 6 if one accidentally enters a date that does not exist, i.e. 06/31/20 it would flag the error. Pan X does not, it changes the date to July 1 for example. If, however you accidentally enter 06/32/20 (a typo) it leaves the field blank.This can be a problem when manually entering dates as we may not catch the change but need the date to be the last day of the month. Bug or feature?

[CooperT]

This issue has come up before:

Two funny things in PanoramaX

Perhaps you think, as I did, that 2/30/19 is not a valid date. But, it turns out, that in PanoramaX 2/30/19 is equivalent to 3/2/19. Although 2/30/20 is equivalent to 3/1/20. So datepattern(date("2/30/19"),"Month dd, yyyy") ==> March 2, 2019 but datepattern(date("2/30/20"),"Month dd, yyyy") ==> March 1, 2020 and datepattern(date("4/31/19"),"Month dd, yyyy") ==> May 1, 2019. But exceeding 31 for day will return an error. For some legal purposes, one year after 2/29/16 will be March 1, 20…

[LeoC2]

Funny I looked to see if it did but nothjing came up, I guess my search criteria was off. Hopefully it gets fixed.

[CooperT]

The title to my earlier post was quite unhelpful to those searching, so I guess I am to blame if someone does not find it.

[admin]

@LeoC2

Bug or feature?

Bug.

I don’t usually pre-announce features and fixes that aren’t yet available, but recently I did a lot of work in connection with validation of data input. This bug is fixed, but there is quite a bit more to it than just a bug fix.

Data Input Validation

[BruceDeB]

I noticed the one example of validating an entry into a numeric field, where the entry was “3 bedrooms” instead of “3” and thought maybe there should be an additional Strip to Number button, to speed up the correction.