Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I'm using the below for sorting purposes.
Timestamp#([Transaction timestamp],'YYYY-MM-DD hh:mm:ss.ffffff') As Timestamp
When multiple transactions are released the very same second, issues occur, even though the "f:s" in the formatting above should be sufficient.
Examples below. Looks like the app has applied the rounding marked in green to the other transactions released 11:31:02 xxxx
Any ideas?
Thanks in advance,
Olle
INPUT DATA | QV ROUNDING |
2014-09-01 11:31:02.467148 | 2014-09-01 11:31:02.467641 |
2014-09-01 11:31:02.467379 | 2014-09-01 11:31:02.467641 |
2014-09-01 11:31:02.467511 | 2014-09-01 11:31:02.467641 |
2014-09-01 11:31:02.467641 | 2014-09-01 11:31:02.467641 |
2014-09-01 11:31:02.467770 | 2014-09-01 11:31:02.467641 |
2014-09-01 11:31:02.467904 | 2014-09-01 11:31:02.467641 |
Rouding is always confusing because of binary decimal precision issue. Could you share your sample qvw that demonstrates the issue?
using this script
t:
load rowno() as id, *;
load * inline [
INPUT_DATA, QV_ROUNDING
2014-09-01 11:31:02.467148, 2014-09-01 11:31:02.467641
2014-09-01 11:31:02.467379, 2014-09-01 11:31:02.467641
2014-09-01 11:31:02.467511 ,2014-09-01 11:31:02.467641
2014-09-01 11:31:02.467641 ,2014-09-01 11:31:02.467641
2014-09-01 11:31:02.467770 ,2014-09-01 11:31:02.467641
2014-09-01 11:31:02.467904 ,2014-09-01 11:31:02.467641
];
I get
I suppose Qlik doesn't take in account all ffffff but only fff (first 3 f)