Toggle the Source

Hello, and welcome again...!

Can we use the same QlikView application for fetching the data from two different database servers if they are having same db name and structure.

We have created two system DSNs with name as ‘MySQL’ and ‘Redshift’ as –

Our target is, to use single “QVW” file where the user should be able to switch between the DSN names. Below are the steps which we can use for same -

• Keep all the column names in small case in views for both MySQL and Redshift Server
• Create a Variable in Qlikview, like ‘vDSN’ which will be used in ODBC CONNECT statement like, and having System DSN name

• Selecting all records from the view using “select *” statement is not a good practice, but as we have only created the views and includes only the required columns, so we have written below statement to fetch the data from views –

• Lastly, add, the RENAME functionality in Qlikview using Mapping LOAD, for aliasing purpose –

• Try to run the code, change the variable ‘vDSN’ and check the result:
• Variable Overview to “MySQL” as –

                Reload the data

               

•      Variable Overview to “Redshift” as 

                         Reload the data

This kind of behaviour, when we have same structure of database, tables, views in different DB servers, and we still want to achieve the same  functionality using single QlikView Application.

Hope this helps.

That's it for this post, stay tuned for more and more articles. Lets give Power to Data...!!!

Whole Story | One place - II

Hello, and welcome all...!

As per my previous post, I have noted down few of the key things, which I like personally in new release of QlikSense. In this article, I am going to tell you few more features, not only related to QlikSense, but also NPrinting and Mobile which Qlik has added in this new Feb 2019 version.

Consider a scenario, where you want to add last refreshed data - date in the email which you are sending as a subscription report to user. Now, in Qlik NPrinting, you have the flexibility to add the variable in the Email part of Publish Tasks as -

This feature also helps in a way, when you want to add the variable in any of the Reports. In Previous versions, we need to add the variable in the NPrinting Designer so that it will be visible in Report, but now, we can also have the same variable used in the Email Message.

Now, we can also have Image improvements in Qlik NPrinting. Suppose, we are fetching any image in the Qlik NPrinting, we can now adjust the Dimensions of same, i.e. Width, height in the Properties window. This feature is only available in Microsoft Office or HTML templates.After upgrading Qlik NPrinting,you must run a metadata reload to see the new Data Displayed width and height parameters under image properties.

In Previous version, whenever there is an error in generating an email, a failure email was sent to user like below -

Now, Qlik has come up with an enhancement, where we can disable this feature. Un-commenting the new parameter <add key="disable-failure-email-sending" />in the scheduler.config file stops emails from sending when report generation fails. If reports are not sent an error will be logged.If you enable this parameter:

• If all reports for a user in a task are correctly generated,the user will receive the email.
• If only some of the reports for a user in a task are generated the user will receive an email with only the generated reports.
• If the generation of all reports for a user in a task fails they will not receive an email.

That's it for this post, stay tuned for more and more articles, lets give Power to Data...!!!

Whole Story | One place

Hello and welcome once again…!

So, Qlik has come up with a new version of QlikSense and i.e. Feb 2019.

It has number of new features like –

•           Improvements w.r.t. usability
•           More visualisations added
•           Mobile features
•           Advance authoring

In this article, I am going to highlight the points which I like the most from this version –

Share button 

Team work, results is good output. This button gives you the flexibility to share your analysis and work collaboratively. You can directly copy the link using this button and share the same through Skype, email etc..

Single Page Tabbed structure

Now, you can have your story, data and analysis in one single page. The way they have kept the tab structure replicates the Qlik Process. So, first you will create data model changes using Data tab, then user will be doing analysis on top of the data and finally creates stories to present or share the outcomes.

Set Analysis $ sign expansion

This is most useful from Developer point of view. How about getting the values of variables and functions in the set analysis editor while creating the expression itself. This is what exactly it does for you, have a look at below image –

That’s it for this article, there are few more things related to NPrinting, mobile features which I will cover in next article.

Stay Tuned…!!!

Mashup Security in QlikSense

Hello and welcome back...!

In one of my previous blogs, we discussed regarding Mashups in QlikView and QlikSense, how we can use them to show near to real time data etc. In today's article, I am going to tell you how Security Rules work in case of Mashups. 

If you want, we can also include few articles on Security Rules, please provide your comment in the comment box below. So, when we say Mashup can have combination of objects from one or different QlikSense Applications, there are possibilities where all users will not be having access to all objects in Mashups. In such cases, how the Mashup will work ?

Consider below scenarios -

1. There is a html link where we have two application objects in one Mashup, and for one application, user is having access and user cannot access the other application in hub
2. There is a web link where the objects in Mashups are from one application only, but user is not having access to the complete application itself
3. User is having access to all objects and application in the Mashup web link

As you can easily guess from above scenarios, for the third scenario, there will not be any problem while accessing the Mashup link. But in case of first and second scenario the behaviour will differ like -

1. In this case, user will be able to access only objects of application which he is having access.  For other objects, there will be blank space 
2. In this case, a blank page will be open with only static content visible

Note: -  In both the cases above, a message will be shown come as a pop-up at the right end corner saying : “Forbidden” 

That's it for this article.

Stay tuned, for more and more articles.

Auto Refresh Near to Live Data

Hello everyone...!

Sorry for delay in posting this blog. Well, as per my one of the blog, we have started a discussion regarding Mashups. We can build mashups in QlikView and QlikSense as well. If you not gone through it, you can read the same by clicking on this link.

So, as promised earlier, I am going to give few more tips and trick regarding Mashups, as most of the development part you can get through Youtube.com, or help.qlik etc.

Now, suppose, you want that your Mashup should get refreshed after few seconds and that too automatically. This scenario comes, when you are presenting near to live data using Mashups.

In such scenario, you can actually integrate HTML features with Mashups. In HTML, if we want to refresh the page automatically, we can simply add below line where the "content" value gives the number of seconds after which the page will get refreshed -

<meta http-equiv="refresh" content="5">

We can add the same tag in our Mashups page, below are the steps for same -

• Login to QlikSense Hub
• Go to Developer hub > Mashups Editor
• Click on HTML page tab which you want to get refreshed. 
• Add above tag inside <Head> tag as -

          <head>

                      <meta http-equiv="refresh" content="5">

         </head>

• Save and test

A small tag and you can play with your near to live data.

That's it for this article. Stay tuned for more articles..!!

New Pie Chart in QlikSense

Hello and welcome all…!

I was planning to continue with my articles on Mashups, but could not resist myself to post an article on a new Pie chart from QlikSense. So, here we go…

Have you ever thought about Pie chart with two measures? So, here in Nov 2018 version of QlikSense, they have come up with a chart called, Rose chart. It’s another style of Pie chart, where you can add two measures, and the radius of the chart defines the second measure – 

Now, suppose, we have –ve values for 2^nd metric, which we will not be able to plot in the above chart. In that case, the Pie chart can be represented as donut chart with –ve values and of course two measures.

Other properties like, Sorting, Alternate states etc., will remain as is.

I really like this visualisation, where you can instantly understand the proportion of the measure to the total. But suppose, if you have many values for dimensions, like products in 100's this might not help. Also this chart takes a lot of space, but of course a good visualisation though.

That’s it for this article. Stay tuned for more and more articles…!!

Mashups in Qlik

Hello, and welcome all...!

Today we are going to discuss regarding Mashups in Qlik. When I say Qlik, I mean QlikView and QlikSense both. If you are not aware, let me tell you that you can create Mashups in QlikView as well.

So, what are mashups..? As name suggested, you can actually include number of objects from different applications in one single HTML page. So, a mashup is a web page or web application that uses content from more than one source to create a single new service displayed in a single graphical interface.

In QlikView, we can create Mashup depending on the requirement using three ways -

• Simple Document - where we can embed the complete QlikSense Document in IFRAME
• Simple Object - where we can embed the complete QlikSense Object in IFRAME
• Div Integration - Where we can embed the objects of QlikView in Div Tag of HTML

Details can be found in below location - 

http://tools.qlikblog.at/QlikView-Mashups/default.html

While in QlikSense, Qlik has provided the Mashup Editor. It can be accessed from Developer Hub which in turn can be accessed through QlikSense Hub. We just have to drag and drop the objects and create Mashups. Qlik also has provided basic templates to start with. Once you select any template, by default, basic structure of files will be created.

We will discuss the Mashup topic in detail in coming posts. Stay tuned...!!!

That's it for this post. 

SDLC to DDLC

Hello Everyone...!!!

Welcome to the another article of the blog series. In this post, I am going to tell you regarding SDLC (Software / Dashboard Development Life cycle) of any Qlik application, I call it as DDLC (Dashboard Development Life Cycle). 

I have gone through number of documents and articles for QlikView Development Cycle. It was one of the things, which is the base of any development in IT industry. If we have proper process for any development, there are very less chances of more numbers of bugs coming in future. 

So, here I have merged all the data related to QlikView Development Process from different resources like blogs, article, Community etc. and of course my own experience.

Dashboard (QlikView) Development Life Cycle:

• (Analyse) Requirement Analysis
• Interacting with Business Analysts and Business users to understand the dashboard, reporting and BI requirements 
• POC Application
• Developer working with the users will create a mock-up of the dashboard to show the users how the data will be presented on the screen. Also discussions should take place on the type of device(Laptop, Desktop, IPad etc.) and screen resolution where this dashboard will be displayed
• (Design) Data Analysis
• Data elements required to full fill user’s requirements.
• (Develop) Development
• Create a data model and visualisations using QlikView Desktop
• Create n-tier QVD architecture o Any object which does not provide insights into data should not be present in the dashboard o Any changes or expectations from client
• (Testing) Review
• Best Practices
• Peer Review
• Debugging
• Unit Testing
• Fine-Tuning
• (Finalise) 
• Deployment on Access Point

This is just the basics of Development Cycle. It will be helpful for me and to others if you provide your valuable comments on this. Please fill free to add any step or any point if I have missed it in the above Cycle.

That's it for this post. Stay tuned, for more articles...