11.2 R4 Bug in Set Analysis

[Anonymous]

I upgraded to 11.2 R4 from R2 on 10/18.  It appears as though there may be a bug in the way they applied one of the updates noted in the release notes stating that ',' is now a special wildcard character under Bug fixes and other Minor Improvements.

Bug fixes and Other Minor Improvements

"Treat single '*', '?', '<', '>' and '=' as Special Wildcard Characters when search

in list box, as well as in a Calculated Dimension, to avoid confusions with the

Wildcard search syntax."

I have a reporting.qvw which we use to distribute excel reports to our managers. Each chart has several different set analysis expressions to calculate fields in the report.

This particular expression

-sum( {$<FinancialMarkersTransGL= {'4','5'} ,fiscal_yr={$(vYear)},prd_of_year={$(vPTD)},day_of_prd ={">=$(=$(FirstDay))<=$(=$(MaxDay))"} >} PostAmt )

In this particular example for the FinancialMarkersTransGL, instead of only summing up Markers 4 and 5, it is now currently summing up markers 4, 5, 57 and 58.  57 and 58 being the only other markers that begin with a 5 that have activity b/w the firstday and maxday.  4 and 5 are the net sales Markers(these are debits), while 57 and 58 are actually asset markers(these are credits).

I have actually downgraded back to Desktop R2 to resolve this problem. Has anyone else has encountered something like this particular incident in the latest Release?

I have submitted this to support,  they requested I submit the QVW for review, but actually the QVW is over 700MBs so I can't exactly send it anywhere.  I will however show the a couple images of the particular column that has been directly affected. These percentages should be in the 28 to 35 range for Cost of Sales.

First column is the bugged calculation after the upgrade. The second column is the accurate calculation after downgrading back to the previous version.

Edit: added reduced version of the file.  The COS tab is the tab that the images above come from.  The attached file is also from after I downgraded to R2.

Edit2: Removed attachment

[rbecher]

Can you please move this discussion into the QlikBug group: QlikBug

[advait_thakur]

This is a very surprising behaviour. Thank you Rodrick for discovering & opening the eyes of others. There must be something to come up with this. If users/customers have upgraded to SR4 then it might hamper many applications, identifying the root cause will be more challenging.

[gussfish]

I completely agree with you, G Wassenaar, that's a shocking design decision, a massive break in backward compatibility.  An error in judgement like that make me wonder if QlikView is now complex enough that it's becoming difficult for QlikTech to evaluate changes; and that QlikTech should start crowdsourcing their design reviews in the QlikView Community so that they get a more complete impact analysis and depth/roundedness of solution.

Angus.

[rbecher · Accepted solution]

Now v11.2 SR4 has been withdrawn, that's what I've expected after this issue was posted:

http://community.qlik.com/blogs/technicalbulletin/2013/10/23/qlikview-1120-sr4-update

I think this set analysis issue has to be fixed..

[Gysbert_Wassenaar]

Looks like this issue was indeed the reason to redo SR4: http://community.qlik.com/blogs/technicalbulletin/2013/10/23/qlikview-1120-sr4-update#comment-10306

[Gysbert_Wassenaar]

This issue is fixed in the newly re-released SR4.