

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ETL in Qlik Sense
Hello,
We actually have QlikView and Qlik Sense products.
In QlikView we have an environment with DATA, STAGE and APP.
In Qlik Sense, we have our applications made in Sense but DATA&STAGE are consumed from QVDs, generated by QVW files (QV).
I wanted to know if that is a good way to implement it, or how could we achieve to get our own DATA&STAGE layers for Sense only?
Thanks.
Accepted Solutions


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe this is a matter of personal preference, and you might get different opinions from different people...
I'd say - if you already own both QlikView and Qlik Sense licenses, and your team is equally good with both tools, I'd keep my ETL processes in QlikView and develop the visual layer in the tool of your choice per application. My reasons for that are:
- While the script language is nearly identical in both tools, QlikView allows a bit more advanced functionality - for example, existing wizards for loading and transforming "dirty" spreadsheets, etc...
- QlikView Publisher is a lot more versatile than Qlik Sense tasks - you can use triggers, pass variables, and use many other advanced features that were not implemented in Qlik Sense.
On the other hand, Qlik keeps developing and enhancing the visual data loading functionality in Qlik Sense. If you'd like to leverage these new "drag-and-drop" data loading capabilities, you might prefer to implement a similar ETL structure in Qlik Sense.
Cheers,
Oleg Troyansky
Upgrade your Qlik skills at the Masters Summit for Qlik - coming to Boston, MA this October!


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe this is a matter of personal preference, and you might get different opinions from different people...
I'd say - if you already own both QlikView and Qlik Sense licenses, and your team is equally good with both tools, I'd keep my ETL processes in QlikView and develop the visual layer in the tool of your choice per application. My reasons for that are:
- While the script language is nearly identical in both tools, QlikView allows a bit more advanced functionality - for example, existing wizards for loading and transforming "dirty" spreadsheets, etc...
- QlikView Publisher is a lot more versatile than Qlik Sense tasks - you can use triggers, pass variables, and use many other advanced features that were not implemented in Qlik Sense.
On the other hand, Qlik keeps developing and enhancing the visual data loading functionality in Qlik Sense. If you'd like to leverage these new "drag-and-drop" data loading capabilities, you might prefer to implement a similar ETL structure in Qlik Sense.
Cheers,
Oleg Troyansky
Upgrade your Qlik skills at the Masters Summit for Qlik - coming to Boston, MA this October!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you have used both, can you give any suggestion... is there a tool like Power Query that can be used with Qlik Sense?
Regards,
Mathew
