Friday 17 October 2014

Keep in Mind When Developing Qlikview Applications

While developing Qlikview projects, from time to time I load new data from data sources. And I have a standard of coding; there are things to be considered each time I load data or create a new app. I would like to keep the records of what I should take into consideration when creating a new app. The list will not be as it is when I am writing this post, I will be adding new items, whenever I find new ideas worth to mention here.

  1. Is your application device specific or single size? You need to know the screen size of the application. This may change from device to device or you may be developing one single app for all kind of devices. In the prior case you will have different apps for different screen sized devices. But in the latter case you will have a single app for every kind of devices those users will have access from. 
  2. Load data in an easily readable format. Remember, in the current selections box, field names looks just as they are in the data model. If they are not easily understandable by a non-tech user then your design lacks. There are two ways to deal with this concern:
    • You can load your fields by giving them aliases. An example to this:
      IncResDate AS [Incident Resolve Date], 
    • If the first option is not applicable, then consider mapping your field names with user friendly ones. You can follow this how to post to do this.
  3. Parameterize attributes and texts those used very often. While you design a Qlikview app, assume that you use the same colour on more than one object. You created your app and your client asked you to change one of the colours you used on many of the objects. In this case you will have to change them one by one, or replace using expression overview on the menu. So, instead of writing these colour codes one by one, create a variable and assign the colour value you would like to use to this variable, and put this variable in place of the colour code text of the object. If you need to change the colour, you will only be required to change this variable, nothing else, shorter isn’t it!
    One another case: If you are creating similar apps and you build one app by copying the previous app, you can parameterize the texts those will be changed in the second app. The cases where you should use variables, depends on the project type and structure.
  4. You may need to deploy some qlikview extensions. In order to make this extensions available on the server, you need to copy extension folder(a folder containing two files, possibly one js, other one xml) under a specific path. This path is :
    Windows Server 2008:
    • C:\ProgramData\QlikTech\QlikViewServer\Extensions\Objects
    • C:\ProgramData\QlikTech\QlikViewServer\Extensions\Document
    Windows Server 2003:
    • C:\Documents and Settings\All Users\Application Data\QlikTech\QlikViewServer\Extensions\Objects
    • C:\Documents and Settings\All Users\Application Data\QlikTech\QlikViewServer\Extensions\Document

    The important task here is to restart qlikview server. Without accomplishing this, you may not be able to you access your extension from the web client.
  5. to be continued..
Hope these items are useful for you.

No comments: