Introducing Qlik Sense June 2017!

[QlikSenseUpdates]

We are pleased to announce the release of Qlik Sense June 2017!

With releases five times per year, it could be difficult to stay up to date on what’s new. The document attached to this post will help you keep up to date.  You will find a look back at some of the key features released over the past 12 months as well as a detailed outline of the the most current release.

But first.... check out this overview video:

Some of the most exciting enhancements in this release include:

• New Visualizations – New visualizations including the Box Plot, Distribution Plot, and Histogram,
• Advanced Analytics Integration – The ability to call out to third party engines (such as R & Python) during analysis.
• Visual Data Prep Enhancements – A wide array of improvements to the visual data preparation capability of Qlik Sense including Visual Data Profiling, Data Binning, Visual Table Concatentation, Data Quality Transformations, Filtering, and inclusion of scripted data sets in visual data preparation.
• On Demand App Generation – User-generated on-demand analysis apps drawn from Big Data.

WHAT YOU SHOULD DO NEXT:

• Customers can visit the Qlik Customer Download Site HERE
• If you are new to Qlik, you can download the Qlik Sense June 2017 desktop version HERE.
• Stay informed and learn more by joining us on an upcoming webinar or local event.

[sirpod90]

Hi George,

that is a nice trick you showed. But in QlikSense the data are already posted over web service. So this workaround doesn't help here

The problem I see is the limit for posting over web service what is hard coded.

So for me the techniques it self is not the best choice, if the data are already in memory...

Regards

Tobias

[gsbeaton]

Hi Tobias - it sounds like something is being lost in translation here.

If you have all of your data already in RAM, then there is no need for ODAG.  ODAG is only useful if you have so much data you need to analyse that it won't fit into one Qlik application.  ODAG then allows you to run a new and targeted set of queries on the database and create a new Qlik application based off that new data set.

It's no more complex than that.

[sirpod90]

What you describing is for me is a typical purpose of document chaining.

My problem is there are to much data for Qlik to handle and be usable.

Mostly I have my data in a Qlik App but all table, plots and other visualization are far to slow to discover anything.

But I see that most people don't understand my point because you probably use qlik for a totally different kind of business purpose and therefore you use totally different kind of data modles.