A Business Intelligence and Data Warehousing public house
Wouldn't it be nice to know what fields are "unreferenced" in your document? By unreferenced, I mean fields that are not used in Expressions, Dimensions or Keys. These are fields that if removed from your document, would have no impact on the visible elements of the application.
QlikView Release Ar
If this is all there’s about Gemini, well I really do not see this as a serious threat to QlikView.
The only thing I really liked about Gemini was the GUI for the tables linking. That’s certainly something QlikView has to improve, but I am sure it will be there soon…
So what do you guys think? I am curious to read your comments
Load from Excel is usually pretty straightforward, but sometimes you'll need to load multiple sheets and make some determinations at runtime. Details such as sheetnames may not be known at script creation time.
The QV statements "SQLTables" and "SQLColumns" may be used to discover information about the sheets and columns available in a workbook. Both of these statements require an ODBC connection. The ODBC connection may also be used to subsequently read the data, but I find using the LOAD biff more convenient.
I recently had a requirement to create a heat map of the US States and set about exploring if there was an easier way than creating a QV scatter plot mapped over an image.
I found the Google Chart API. With some help from the QlikCommunity forum, I got a fairly pleasing result.
QlikView - extract data from comma separated cell
QlikView - Export chart data on specific date to xls file
Concatenate and NoConcatenate
I attended Niklas Boman's excellent Performance Tuning talk at Qonnections in Miami. One of his tuning recommendations was to reduce the number of rows and columns when possible. This will probably always have a positive impact on chart calculation time, but if done incorrectly, reducing the quantity of data can have an adverse impact on RAM usage.
You can run QlikView from the command line. You've probably created shortcuts on your desktop to various useful QV reports. In that kind of shortcut the command is simply the complete pathname to the report file. That will also work in a .bat or .cmd file; just enter a usable pathname to the report file and Windows will open QlikView for the report.
a much simpler way to make the report smaller is to select the data you are interested in retaining and then, from the menu, select File->Reduce Data->Keep Possible Values.
f you're going to sit at your desk in front of the computer and watch it run then you don't have to do anything -- any loadscript error window that opens up can be clicked and the report can be cancelled if necessary. But, if the report is going to load unattended without anyone watching then consider these actions
If you are using the macro code Reload method to load data into your QlikView report you can also easily check for any loading errors. Here's an example of how that could be done.
I had a large report that we needed as an example for a presentation but it was just too large. The original database it loaded from is no longer available, so I needed a way to make the report smaller without reloading it. It had one large shipment data table in it and I decided to change the the table to only include two shipping location codes which would make it much smaller.