Max Date and time is not getting converted in appian

RE: Max Date and time is not getting converted in appian

Stefan Helzle — Wed, 25 Oct 2023 07:58:34 GMT

I do not have a good solution to this. I assume that this date has specific business meaning. If this is the case, I would challenge this. Using specific values to indicate something is pretty dangerous.

If you are willing to accept that your application has a problem with the date 4/10/2292, you could just check for this date and display 9999-12-31 instead. I do not recommend this.

RE: Max Date and time is not getting converted in appian

Sameer Ul Haq — Wed, 25 Oct 2023 06:58:27 GMT

9999-12-31 is the date expected to show in Interface is their a way to achieve that in recordlist without altering the data in datasource.

RE: Max Date and time is not getting converted in appian

Stefan Helzle — Thu, 31 Aug 2023 12:57:26 GMT

OK. I did a quick test.

In DB I see this:

In Appian (switched my user to GMT):

Going to 9999-12-31 in DB does not work. I assume this is not a valid date.

This seems pretty much OK for me and I consider this to be a slight variation in handling certain edge cases.

Do you have the chance to change this value in DB?

RE: Max Date and time is not getting converted in appian

Sameer Ul Haq — Thu, 31 Aug 2023 12:38:41 GMT

Yes still the same.

RE: Max Date and time is not getting converted in appian

Stefan Helzle — Thu, 31 Aug 2023 12:05:34 GMT

When querying the data more direct, not synced, is it the same?

RE: Max Date and time is not getting converted in appian

Sameer Ul Haq — Thu, 31 Aug 2023 12:01:23 GMT

Its the same 4/10/2292 11:47 PM

RE: Max Date and time is not getting converted in appian

anmolvijayvergiya — Thu, 31 Aug 2023 11:57:16 GMT

It could be a time zone settings issue.

RE: Max Date and time is not getting converted in appian

Stefan Helzle — Thu, 31 Aug 2023 11:54:51 GMT

As per the documentation Appian seems to support that.

https://docs.appian.com/suite/help/23.3/Appian_Data_Types.html#date

But, do you see the same behaviour without the datetext() call?