|
=DateAdd("s",Fields!TimeStamp.Value,"1970-01-01 00:00:00") |
|
S.No |
Expression Name |
Expression |
Comments |
|
|
Expression1 |
FROM_UNIXTIME('1497855166') |
Convert 1497855166 this time stamp value as date |
|
|
Expression2 |
FROM_UNIXTIME([UnixTimeStampColumn]) |
Convert UnixTimeStampColumn value as date |
|
S.No |
Expression Name |
Expression |
Comments |
|
1 |
Expression1 |
datetime('1497855166','unixepoch', 'localtime') |
Convert 1497855166 this time stamp value as date |
|
2 |
Expression2 |
datetime([UnixTimeStampColumn],'unixepoch', 'localtime') |
Convert UnixTimeStampColumn value as date |
We have tried to make use of datetime('1497855166','unixepoch', 'localtime') Emergency Locksmith Doncaster in order to convert our timestamp values to datetime values. But the expression column isn't being seen as a datetime but rather as string. How can we go about resolving this?
Hi Ali Raza,
Could you kindly confirm whether you are seeking a solution on the Classic Dashboard Platform or Bold BI?
If it is Bold BI, please find the response details below:
Upon thoroughly reviewing your inquiry regarding the conversion of timestamps using datetime functions—specifically your observation that such conversions result in string-type columns instead of DateTime-type columns—we would like to provide some clarity on this matter. This behavior occurs because Bold BI's expression engine does not inherently infer the data type from SQLite-style expressions.
To address this issue and ensure that your expressions are properly recognized as datetime data types within Bold BI, we recommend adhering to the following guidelines:
1. Instead of relying on SQLite-style datetime() functions, opt for Bold BI’s supported expression syntax to achieve the desired data type.
2. For SQL-based data sources, you may employ the following approaches:
- In SQL Server, use the expression: DATEADD(SECOND, [UnixTimestamp], '1970-01-01').
- In PostgreSQL, use the expression: TO_TIMESTAMP([UnixTimestamp]).
Additionally, please ensure that the [UnixTimestamp] field is represented in seconds rather than milliseconds. If the timestamp is provided in milliseconds, you will need to divide it by 1000 to convert it into seconds. Should you have any further questions, concerns, or require additional assistance regarding this matter, please do not hesitate to reach out to us. We are here to support you.
Regards,
Rajendran Murugan
We have tried to make use of datetime('1497855166','unixepoch', 'localtime') in order to convert our timestamp values Locksmith Sheffield to datetime values. But the expression column isn't being seen as a datetime but rather as string. How can we go about resolving this?