Hi Claire, i would suggest doing this in the LOAD EDITOR so that you don't load excess granularity in the dashboard. Whether you do the following in the load editor or the master item dimension definition , the syntax is the same.
Lets say your datetime field is [DateTime].
Date(floor([DateTime]) , 'DD/MM/YYYY')
In the script you would add an alias:
Date(floor([DateTime]) , 'DD/MM/YYYY') as Date,
- qlik interprets all dates as numbers. a whole number is a day and the decimal is the time portion
- the floor function will round down the number to a whole number effectively giving you a date without any time context
-then use the date() function to format the number in the date format you want.
- sometimes qlik sense can't interpret your raw data field as a date or date time without help
- to help it out, provide the format of the date that you expect using the date#() function. Date#() is a date reading interpretation function / Date() is a date display function.
so if your date times are in the database as DD/MM/YYYY hh:mm:ss format then you can use this:
keep in mind that if your hours are stored as 1:00:00 you would use h:mm:ss . If they are stored as 01:00:00 then you use hh:mm:ss. Its very granular
Put it all together and you have something like this where you are reading date in a specific format, dropping the time, and display in a specific format all at once:
Date(floor(Date#([DateTime],'DD/MM/YYYY hh:mm:ss')) , 'DD/MM/YYYY') as Date,
sometimes you have milliseconds (fff) and AM/PM to deal with too. Here are the masks for those as well
Date#([DateTime],'DD/MM/YYYY hh:mm:ss.fff TT')
good luck !
Thank you Jonathan, that's worked a treat!
I created my field in the Master Items. How should I go about creating it within the Load Editor? In the Load Editor I have 'Main' and then my 'Auto-generated section' which is locked. Should I unlock that and add at the end of the code?? I'm nervous about unlocking it........
Thank you as well for the explanation. Understanding how Qlik works compared with other applications I've used is hard because you know the formula you want but not how Qlik wants you to write it. I'm struggling a lot in this area at the moment as I look to get to grips with it so you may see me popping up with other questions on how to write some formulas.
You can unlock it but it will disable the 'add data' and 'data manager' features for the app moving forward.
You could also add a new section to the load editor to come after the locked section. Hit the '+' icon in the data load editor ( i think its bottom left by memory) to add a new section and drag it to the bottom of the sections on the left side.
In the new section, create a new table called 'Dates' which will load all your dates and bucket them.
month(Datefield) as Month,
year(Datefield) as Year
for <existingdatatable> , go to the 'data model viewer' and look at the name of your existing table, and use that name without '<>' characters after 'resident' . Its called a resident load of data that you already loaded in. For this purposes you are creating a calendar table with some pre-built functions. This way you populate all the potential date buckets in advance.
Sorry for the late reply, there's been a lot going on at work recently.
I've created a Variables table in the load editor where I would like to try and create many of the additional variables I need and have tried using the week commencing date one as an example using your script example.
When I debug the code, I get a red line in row 2 so I can't be scripting correctly. I've used SAS and SQL in the past so naturally I think along those coding principles and languages. Can you tell me where I'm going wrong?
Date(floor([Week Commencing]) , 'DD/MM/YYYY') as "Week Comm"