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.
How are you building the generated App? In my case, I have to prepare it in a certain way with a specific syntax :
Example of one of myGeneratedApp script:
// DO NOT ALTER THIS SUBROUTINE
SUB ExtendWhere(Name, ValVarName)
LET T = Name & '_COLNAME';
LET ColName = $(T);
LET Values = $(ValVarName);
IF len(Values) > 0 THEN
IF len(WHERE_PART) > 0 THEN
LET WHERE_PART = '$(WHERE_PART) AND $(ColName) IN ( $(Values) )';
ELSE
LET WHERE_PART = ' WHERE $(ColName) IN ( $(Values) )';
ENDIF
ENDIF
END SUB;
// CHANGE 1: Update these SET statements to correspond to the names of the fields from your Shopping Cart app.
// The contents inside the $() on the righ-hand-side of the first SET statement of each of these
// must match the names of the fields from your shopping cart app that the user can create selections on.
// If the database column name for any of the selection fields has a different name, you need to alter the
// right hand side of the second SET statement to reflect that field's corrresponding database column name;
//
// All fields for On Demand are prefixed with od and the following to indicate selected or associated or NOT associated
// ods = Selected values
// odo = Associated values
// odx = Excluded vlaues
// odso = Selected/assocaited values
//
SET Year =;
SET Year = $(odso_MyYear2_n);
SET Year_COLNAME = 'Year';
SET TerritoryCode = ;
SET TerritoryCode = $(odso_code)[2-4];
SET TerritoryCode_COLNAME = 'TerritoryCode';
SET CarSales = ;
SET CarSales = $(odso_CarSales);
SET CarSales_COLNAME = 'CarSales';
// CHANGE # 4: Replace this with your CONNECT statement
LIB CONNECT TO 'Microsoft_SQL_Server_localhost (win-d1qku4urkte_administrateur)';
// CHANGE #2: Alter this with a leading 'WHERE <condition>' if you want your SQL statement (below)
// to have a non-changing WHERE clause in addition to the clauses that will be inserted
// by the shopping cart app (it is fine to leave it as is).
SET WHERE_PART = '';
// CHANGE 3: Update the list of field names here to reflect each of the field names variables you have on the
// left hand side (assignment target) of the first SET statement of the SET statement pairs in change
// 1 above.
FOR EACH fldname IN 'TerritoryCode','CarSales','Year' //'ORIGIN', 'DEST', 'YEAR', 'QUARTER', 'ORIGIN_STATE_ABR', 'DEST_STATE_ABR', 'TICKET_CARRIER', 'FARE_CLASS'
LET vallist = $($(fldname));
WHEN (IsNull(vallist)) LET vallist = '';
IF len(vallist) > 0 THEN
CALL ExtendWhere('$(fldname)','vallist');
ENDIF
NEXT fldname
TRACE Generated WHERE clause: ;
TRACE $(WHERE_PART);
// CHANGE # 5: Replace everything EXCEPT the $(WHERE_PART) portion of the SQL SELECT statement with
// query you wish to send to the database. Note that you can have more than one of these
// dynamiclly alterered SELECT statemnents by replicating the sections from CHANGE #2 thru this
// change #5 and customize which WHERE clauses will be inserted by altering the list of fields
// in the FOR EACH statement in Change #3.
Load*,
num(Timestamp( MyYear2_n,'YYYY-MM-DD hh:mm:ss.SSSSSS')) AS MyYear;
//num(MyYear2_n) as yearr;
LOAD Year as MyYear2_n,
TerritoryCode as code,
CarSales,
[Car production],
[Cars in use],
[Commercial vehicle sales],
[Commercial vehicle production],
[Commercial vehicles in use],
[Motorization rate];
[WorldVehicleData]:
SELECT "Year",
TerritoryCode,
CarSales,
"Car production",
"Cars in use",
"Commercial vehicle sales",
"Commercial vehicle production",
"Commercial vehicles in use",
"Motorization rate"
FROM SSIS.dbo.WorldVehicleData
$(WHERE_PART);
Then, in the selection app; I have my model and the extension that call this app
The built in version is the same selection app/detail app with the variables, it also contains extra script to build the where clause as an inline load to allow more values
icd, I'm currently trying the Qlik Sense June 2017 server ; there is something I don't really get :
There is a published application; I want to add a new sheet ; I thus edited an existing sheet(from the base sheets) and wanted to perform my modification BUT the FIELDS logo is MISSING !!!
But I can access to the fields on the existing charts and thus change the expressions/dimensions !
Why that??
Don't tell me you've altered again the by default rules?! It makes no sense what so ever !
I think that's standard behaviour for a published app and has been on previous releases - you only see the master items in the left hand panel, but can access the field list in the expression editor. I imagine it's to promote self-service users making use of the master items...
This has been the default behaviour since version 1.0, a published app can use the master items created by the app designer to create new visualisations
Hi Harish, Unfortunately we are unable to respond to support questions here. Personally, I upgrade with each release and have not experienced any issues. If you are working with desktop, I would suggest uninstalling and reinstalling Qlik Sense. Thanks PeggySue
