Hi,
I have a date time field in DB stored with max value 9999-12-31 00:00:00.000000 i have a record type synced with this DB column field as date time type. when i am querying the record from Appian I am getting 4/10/2292 11:47 PM as result. when i verified the field in the record list this expression is used
if( isnull(fv!row['recordType!{dd3dec1e-fa8b-4d23-b987-227710abaa1b}PM Processdir.fields.{cad2d16f-825b-49a8-a577-aeb727fb031d}dueTs']), fv!row['recordType!{dd3dec1e-fa8b-4d23-b987-227710abaa1b}PM Processdir.fields.{cad2d16f-825b-49a8-a577-aeb727fb031d}dueTs'], datetext(fv!row['recordType!{dd3dec1e-fa8b-4d23-b987-227710abaa1b}PM Processdir.fields.{cad2d16f-825b-49a8-a577-aeb727fb031d}dueTs'], "default") )
Discussion posts and replies are publicly visible
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?
Its the same 4/10/2292 11:47 PM
When querying the data more direct, not synced, is it the same?
Yes still the same.
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?
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.
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.