Dates viewing and exposing in different formats
Matthew Davis (Technical Product Manager) 5 years ago • updated 4 years ago • 3
When a date field is configured on a connector / adapter in UNIFYBroker, it displays in the entity view table in a friendly format (such as 04/Jul/2014). However, when exposed into a PowerShell transformation or downstream, it is exposed in a different format (2014-07-04T00:00:00.000)
This is also true for the Timestamp field, which displays in the entity view table as something like 04/07/2014 12:00:00 AM
It would be good if you could see the raw date format as exposed by the gateways, as well as a formatted date for easier reading.
It would also be good to get some consistency across the formats that are displayed in the entity view tables.
Customer support service by UserEcho
Isn't it a DateValue or TimestampValue? In which case standard .NET DateTime operations work on it.
I think this should be consistent with the date format, would this help? The original intention with the date was that it was globally recognisable.
Where do you want to see this, in the entity viewer? How would this work, as different gateways have different standards that they're adhering to, for example LDAP requires a much different format to REST based protocols?
Thanks for the response.
I think the main confusion lies in the display difference between the DateValue and TimestampValue in the entity viewer.
If you attempt to use a Parse operation on the DateValue in a powershell transformation, you may initially assume that the date is in the value 04/Jul/2014 which is in fact not the case.
I understand that gateways each have their own way of outputting different date and time values, not much way around that. Perhaps it would just be best to have a consistent display of both Date and Timestamp values in the entity view table.
This is not a priority, just an idea to simplify data consumption by product users.