Book Image

QlikView Scripting

By : Matt Floyd
Book Image

QlikView Scripting

By: Matt Floyd

Overview of this book

<p>QlikView is a powerful business intelligence and data discovery platform that allows people to quickly develop relevant data visualization applications for business users. The relative ease of QlikView development—including backend scripting—allows applications to be developed rapidly, and allows for more collaboration in application development for business users.</p> <p>A comprehensive guide that offers QlikView developers a rich discussion of scripting topics, from basic to advanced concepts, features, and functions in a compact mini-book format. This book allows developers to quickly gain confidence in understanding and expanding their QlikView scripting knowledge, and serves as a springboard for even more advanced topics in QlikView scripting.</p> <p>The book starts off by covering basic topics such as connecting to data sources, scripting, dealing with load statements, data transformations, and the concepts of the basic data model. It then dives into advanced concepts such as advanced scripting and data model optimization, the creation and use of QlikView datafiles, debugging, and essential functions and features. It also provides layout tips for developers. Qlikview Scripting is a great overview and reference guide for beginner to intermediate Qlikview developers.</p>
Table of Contents (16 chapters)
QlikView Scripting
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Debugging using logfiles


Script logging for the current QlikView application can be activated by opening the Document Properties dialog, General tab. If the Generate Logfile checkbox is selected (as in the following screenshot), QlikView will create a logfile of the script execution (the output will be as seen in the Script Execution Progress dialog when you run the script). This file, with the default name qv.log, is stored in the same folder in which the current QlikView application is. If you activate the Timestamp in Logfile Name checkbox, the file name is saved with the current script run time stamp in the logfile name.

The logfile is usually the first place to look for errors if a load fails or displays errors and is a key tool in your debugging. Find the errors in the logfile, and work through your script again to spot the errors using the debugger and Exit Script function to help you isolate the errors.

You can place a custom text that is displayed in the Script Execution dialog and...