Date out of Date out of range (-740126)

RE: Date out of Date out of range (-740126)

vikrams247 — Mon, 11 Jul 2022 08:00:55 GMT

Thank you for your kind reply. this was happening due to bad data and has been taken care by our DB team.

RE: Date out of Date out of range (-740126)

vikrams247 — Mon, 11 Jul 2022 07:58:52 GMT

Hi Mike,

Thank you. This was Out DB issue and most was bad data. This has been take care by our DB team.

RE: Date out of Date out of range (-740126)

davel001150 — Tue, 14 Jun 2022 14:04:25 GMT

Since the values are different, I assume this has to be a casting or transformation error. Perhaps it's presented to a rule in one format, saved in another, sent to the database in another, and then you try to cast it as a date, and Appian breaks.

What if, for instance, something misinterpreted 08/26/2008 as 8 divided by 26 further divided by 2008, or 8,262,008? What if the timestamps rolled into some faulty calculation? Are they a Date column in the database, or a Date and Time column?

By the way, todate(-73992) comes out to a date in 1832, about 190 years ago. So if Appian accepted these dates, they'd be somewhere in the first or second century AD, around 1900 years ago.

RE: Date out of Date out of range (-740126)

Mike Schmitt — Tue, 14 Jun 2022 12:52:08 GMT

In the DB itself, do those rows have valid dates? As opposed to, say, NULL values? In what manner was this data originally populated? If you manually edit the value found in the target column of one of those rows, directly in the DB, does it fix the front-end output from Appian?