Qlik Community

New to QlikView

Discussion board where members can get started with QlikView.

Announcements
Announcing the newest addition to the Qlik Community, Qlik Gallery! Learn More
Highlighted
barakovskikh
New Contributor III

Qlikview 11.20 SR19 CRITICAL TROUBLE

Hi! Beginning with QV 11.20 SR 16 and upper application confuses fields and data during calculations.

1. Open the application

2. Reload document

3. = Bug (See 1 screnshot in attachment) <- Field 1 = Field 2 & '|' & Field 3

4. Do not close document and reload again (See 2 screnshot in attachment) = all good!

Bug actual for desktop (QV) and server (QVB) load

Spoiler

tmp:
NoConcatenate
LOAD * Inline [
x,y,z
];

Concatenate(tmp)
LOAD
RowNo() as x
,RowNo()*-1 as y
,RowNo() as z
AutoGenerate(100000);

DATA:
NoConcatenate
LOAD
x & '|' & y as KEY,
x,
y,
fabs(z) as z
Resident tmp;

drop Table tmp;

First load after open document

clipboard_image_0.png

Second load after open document

clipboard_image_1.png

 

 

Labels (1)
59 Replies
barakovskikh
New Contributor III

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

UPD: If you insert such code at the beginning of the script, all of the following code will be considered correct. I.e. failure likely goes to 1 of the computation, fabs,sign and other.

 

Spoiler

FIX:
NOCONCATENATE
LOAD
FABS(ROWNO()) AS Z
AUTOGENERATE(1);

DROP TABLE FIX;

  

 

Leshiy_Prophet
New Contributor

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

I confirm. We also reproduce the problem.

barakovskikh
New Contributor III

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

UPD:

First load

clipboard_image_0.png

Second load 

clipboard_image_1.png

MVP & Luminary
MVP & Luminary

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

With 11.2 SR12 I could not find any issue by this example ...

- Marcus

barakovskikh
New Contributor III

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

Hi! This bug starts with 11.20 SR16 and above i.e. SR16, 17, 18, 19

You can install desktop any of 11.20 sr16-19 and check the example.

MVP & Luminary
MVP & Luminary

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

11.2 is (nearly) out of support. Therefore it would be more interesting - does it exists within the QV 12 releases, too?

- Marcus

barakovskikh
New Contributor III

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

Qv.12.40 does not have this bug.

But us interested in 11.20 on latest SR because transition on QV 12 for us will not soon.

The transition to version 12 is more difficult than updating SR within one version.

MVP & Luminary
MVP & Luminary

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

Please open for it a support-request. Even if they couldn't comprehend the issue or deciding not to develop a regular or custom bug-fix they might be able to give hints to bypass it.

Personally I would assume that such an issue should occur more randomly and not by the first load and after a second load everything is working again. Therefore it could be useful to wrap it in a loop to repeat it n times and checking each time the results with noofrows(), fieldvaluecount() and so on. Further would be interesting what would be stored in a qvd - right/wrong data - and how did it change if you load your final data from a qvd (maybe this is already a practically bypass).

- Marcus

barakovskikh
New Contributor III

Re: Qlikview 11.20 SR19 CRITICAL TROUBLE

1.Saving\Load DATA in\from QVD gives wrond data too. Bug not only for inline load

2. If before this script insert here is this for example, then bug, too, is missing.

(For a workaround, we can use include (..) with this script)

FIX:
NOCONCATENATE
LOAD
FABS(ROWNO()) AS Z
AUTOGENERATE(1);

DROP TABLE FIX;

3. The error occurs only when mathematical functions such as fabs, sign, and others are used in the script.

Therefore, the script above uses fabs to fix the problem in the script below.

The loop also solves the problem, because only at the first collision with mathematical functions the data breaks the integrity

So! The problem occurs only at the first operation in the script using mathematical functions and only at the first update of the application.

4. The NoOfRows function always gives the correct result, but Field Value Count in KEY gives less for first pass

5. Bug repeated on several PCs, It's more like mysticism. More I do not understand how after the bug it is not fixed for the next 3 SR