I'm down a rabbit-hole regarding the M-Files DataType Time (not Timestamp), ID 6.
In UIXv1 we had M-Files COM Methods GetValueAsLocalizedText and GetValueAsUnlocalizedText - as far as I can see those do not exist in UIX v2 framework, so we need to implement them somehow. That raises the question:
Does a property of DataType Time have an implied time zone, i.e. will it be displayed differently to users located in different time zones?
Specifically UIX v2 will return a TypedValue object of the following form, representing "9:11:24 PM" in US English locale:
{
"type": 6,
"is_null_value": false,
"data": {
"time": {
"seconds": "-11644397316",
"nanos": "0"
}
}
}
How should we convert this to
a) a localized display value
b) an unlocalized string, independent of time zone and regional settings (for categorization purposes).
I noticed that the following JS code will magically generate b), i.e. output "211124Z" corresponding correctly to 9:11 PM and 24 seconds
const date = new Date( obj.time.seconds * 1000);
const str = date.getUTCHours() + date.getUTCMinutes() + date.getUTCSeconds()+ “Z”;
However, using the non-UTC JS Date methods was unsuccessful, it generates the weird result "22:04:52 GMT+0053 (Central European Standard Time)" - my current time zone is UTC+0100 CET. But maybe we don't need it if M-Files Time properties are to be understood and displayed in one time zone (presumably UTC) - i.e.every user around the world sees the same value?
