This field is required.
Only these extensions are allowed(.jpg, .JPG, .jpeg, .JPEG, .gif, .GIF, .png, .PNG)
Tags cannot contain the characters ' /, \\, #, ?, or ; >,< '
Only these extensions are allowed(.zip,.ZIP,.pdf,.PDF,.qvf,.QVF,.qvw,.QVW)
Discussion Board for collaboration related to QlikView App Development.
Lately, I was trying to load the string type date data from my work DB.
But it was so hard because qlikview converts this data to unix-time data for itself.
After all, I succeed this work converting the string type data to that I wanted to data,
but now I'm curious what happened in qlikview process that converts the data type.
Could anyone explain why this auto-converting happen and how can I handling this auto-converting with any setting in qlikview for me, please?
Did you ever notice the SET statements at the beginning of a script?
They are the responsible for the auto-conversion. Every time Qlik loads data, it will check if the data follow the patterns indicated in these SET statements. If positive, it will auto-convert.
See the Help for more info:
"The variables are included at the top of the script of the new QlikView document and substitute operating system defaults for certain number formatting settings at the time of the script execution. They can be deleted, edited or duplicated freely."
First of all, thank your replying to my question.
I did check the SET statement and confirm the date type set with what likes to 'YYYY-MM-DD HH:mm:ss' not unix-time.
But the auto-conversion to unix-time type, not to the type set with SET statement was keeping on.
It's so weird...