Qlik Sense Extensions - Pros and Cons

-


As we know, extensions provide additional functionality that extend the capability of many products. QlikView has his own capability, however Qlik Sense does not provide inbuilt great visualizations. Here extensions play major role, enhancing the look and feel of the product to next level.

Visualization Extensions are a possibility to extend the visualization capabilities of Qlik Sense by using only standard web-technologies. The concept of extensions in general can also be seen as a plugin-mechanism which allows developers to combine the power of Qlik Sense’ APIs with the nearly unlimited capabilities of the web.

Having said this, there are certain reasons, why one should not use the extensions. Following are some of the pro and cons of the extensions for the Qlik Sense.


PROs    
CONs
-------------------------------------------------------------
-------------------------------------------------------------
The quickness and ease of building tables, charts, graphs, etc. in the front end.
There is a distinct lack of technical resources when you are not dealing with sales and financial data.


User friendly Fast Response Responsive design Access everywhere Doesn´t work with all the browsers
Initial steep learning curve to get up to speed Set Analysis is not easy to pick up - misplace a bracket at your peril


Ease Of Use Set up to Delivery Design, look and feel. Flexibility of platform, open APIs Frequency of Development
Collaboration and annotation is not that great. No in-built data governance options. Master data management is not available.


+ Easy to use, + Qlik's associative data model, + Qlik Sense's user self-service functionality/ self-service BI
Qlik Sense still lacks some functionalities and features that are so useful in QlikView. For example, Alternate States and AND-mode.



Being third party and freeware, no post implementation support is available.
 

Comments

  1. James ZicrovApril 29, 2019 at 6:17 AM

    I really think there is a high need of undertaking Qlik Sense and its applications in day-to-day programming and database connectivity operations.

    qlik soap api connection.

    ReplyDelete
  2. Chris LesnarJuly 16, 2021 at 7:51 AM

    This comment has been removed by the author.

    ReplyDelete

Post a Comment

Popular posts from this blog

Qlik Sense Data Reduction (Dynamic)

-
Image
Qlik Sense Data Reduction using Section Access (Dynamic) Qlk Sense supports the dynamic data reduction feature, by which some of the data in an app can be hidden from the user, based on the section access login. • Fields (columns) can be hidden by using the system field OMIT. • Records (rows) can be hidden by linking the section access data with the real data: The selection of values to be shown/excluded is controlled by having one or more fields with common names in section access and section application. After user login, Qlik Sense will attempt to copy the selections in fields in section access to any fields in section application with exactly the same field names (the field names must be written in UPPER CASE). After the selections have been made, Qlik Sense will permanently hide all data excluded by these selections from the user. "All field names used in the transfer described above and all field values in these fields must be upper case, because all fie...
Read more

Understanding Joins

-
Image
JOINS Joins in data model should be used wisely otherwise there may be possibility of things going disastrously wrong. However, it is advisable to keep minimum branches while designing schema. QlikView uses for types of Joins, theoretically it is same as SQL Joins, but there is slight difference in syntax. SQL uses INNER, LEFT, RIGHT and FULL whereas QlikView uses INNER, OUTER, LEFT, JOIN. It’s better to use proper Join wherever necessary. The easiest way to flatten the data model is to join two tables together into one. For a table, where there is a key field and a description, it is very easy to add the description into the main table using a LEFT join (refer to the following section for an example.) Data is joined using all the matching fields in the Load statement, so care must be taken to ensure that all fields needed are included in the Load statement and that any field that is not needed as a link is aliased. A further consideration is that if there are any duplica...
Read more

What is Synthetic Key?

-
Image
Synthetic Key Basics When two or more tables shares more than one common field, QlikView join tables with all fields in common, and this creates an additional table with fields which share both tables. An example of a data model with synthetic keys. Qlikview automatically associates common fields, created a synthetic key or complex key and leading to a third table called $Syn 1 Table. This is the synthetic table which stores the combination of values for the two fields which, form the synthetic key. The synthetic keys in a data model can cause the application to have slow response time and sometimes even consume all available resources. Therefore, need to be avoided when possible.  How to eliminate synthetic keys? There are number of ways, we can avoid QlikView to form Synthetic Key. 1. Using QUALIFY This enforces QlikView to qualify all/selected fields. Qualify implements the check on full path of the field (e.g. Field is created as combination of T...
Read more