When adding an expression to a list box, one of the common complaints is that the numbers displayed are devoid of any number formatting. This is especially frustrating when displaying large numbers without commas to ease readability.
What most beginning report developers try is to format the values with the Number tools in the list box’s properties.
While developing a report, you may be loading thousands if not millions of records during the execution of your script. If you are making edits to your script, and require a reload of the data to test your script changes, you may find yourself spending …
Because QVD files load SO MUCH FASTER than the original data sources (i.e. Excel, Access, TXT, etc…), you may wish to save all of your tables to QVD files. There are a couple compelling reasons to do this: You wish to develop your report in …
It’s every chart maker’s dream to have dynamically changing titles (well, that and a coffee table that looks like a giant floppy disk. Seriously; Google that one if you haven’t seen it. It’s pretty cool.) Any-hoo… To have a chart’s title change based on data you are, or are not, filtering by is a real boon to understanding the story that the chart is trying to tell. Take the following example:
The reader of the chart can look at survey data for four categories all at once as a combined assessment, or they can filter by a specific category and evaluate the ratings individually. If the chart were to be printed, the reader would not have much of an indication as to whether the chart was displaying all categories or focusing in on a single category.
Suppose you want your QlikView report to automatically reload its data based on a schedule. The manual process would be for you to open the report, click the RELOAD button, and then close the file. If you team up the QlikView report with the Windows Scheduler, you can have this reload take place without human intervention.
Open Notepad and enter the following text:
— For users running the 64bit edition of QlikView —
“C:\Program Files\QlikView\QV.EXE” /R “C:\MyQVData\MyQVFile.qvw”
— For users running the 32bit edition of QlikView —
“C:\Program Files (x86)\QlikView\QV.EXE” /R “C:\MyQVData\MyQVFile.qvw”
(Change “C:\MyQVData\MyQVFile.qvw” to the location and name of your QlikView document)
The goal of every QlikView developer is to do as little work as possible. When you notice that you are writing the same instructions in multiple app scripts, the notion of re-use is a red flag that flies with great fervor. QlikView’s Include statement provide just such an ability.
The advantages of re-using scripts between multiple apps has several advantages:
As with anything in life, every “pro” must be accompanied by a commensurate “con”. In this case, the risk of using Include files to re-use script code lies in the fact that the file containing the script must remain in the same location and the file’s name must remain unchanged. If either of these two events occurs, the portion of the script pointed to by the Include statement will not execute.
One of my pet peeves (wouldn’t that be a great name for a dog; “Peeve”?) when working with charts in QlikView is that I have a tendency to click on bars accidentally when showing data to colleagues. When I do, all of the bars disappear except for the bar I mistakenly clicked on. And for that millisecond in time, everyone receives a mental jolt that I wish would rather not have happened.
Since I was trying to direct their attention to a particular month, I think a better behavior would have been for the bar to change color to visually separate it from the herd.
I know what you’re thinking; “But how can a QlikView designer, like myself, enable such a behavior?” I’m glad you asked. Here’s the trick.
The data transformation tools in QlikView are amazing. When I think of the hours I have spent working with data that was output by some system trying to get that data into a format that I could then START modeling. Oh, the wasted man hours.
One of the QlikView transformation tools has the ability to take a crosstable (like a pivot table in Excel) and convert it into a straight table; a traditional flat table where data typically starts.
The only problem with this tool is that it converts all of the data in the crosstable into straight text. This means that even if you see data that looks like a date (ex: 11/25/2015), it is really just a collection of numbers and slashes. QlikView does not understand what these numbers represent. This makes modeling the data a bit problematic.
What is QlikView? Creating Dashboards using QlikViewWatch this video on YouTube In this webinar, you’ll see how to create dashboards and data visualizations with data from Excel and other data sources using QlikView. For more on our QlikView Training Courses visit our QlikView Training page.