topic Re: Issue with the Peek function in qlikview version 12.40.20400.0 in App Development

Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Thu, 24 Mar 2022 04:26:37 GMT

Hi All,

Qlikview peek function is working fine in the version 12.10.20600.0 but it seems that it is not working as per the exceptation on the version 12.40.20400.0.

It is returning more than 1 record.

Could you please suggest on this?

Also the comparison variables are not working without num function.

Below is the snapshot for the error in the Qlikview version 12.40.20400.0,

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Thu, 24 Mar 2022 04:25:10 GMT

Hi All,

Is there any suggestion on this.

Below is the snapshot for the error,

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Thu, 24 Mar 2022 09:50:20 GMT

I assume that your error isn't related to peek() else to the content which you fetch with it or to the way how it's later interpreted. This means your dates aren't dates anymore else strings and/or their format has changed in any way.

You may apply something like:

TRACE $(vBD);

below the peek-statements to see within the progress-window or within the document-log which content is really there.

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 08:16:10 GMT

Hi Marcus,

Can you please have a look at the below code?

Loop1:
LOAD Distinct
//ACCT_SYSTEM_PORTF_NO_PERF as PortLoop,
ANALYSIS_DATE as AnLoop,
BUSINESS_DATE_PERF as BDLoop

Resident PERF_TEMP Order By BUSINESS_DATE_PERF,ANALYSIS_DATE; // MonthNo>='$(vMaxMonth60)' and ACCT_SYSTEM_PORTF_NO_PERF,

let numRow= NoOfRows('Loop1');

sub Loop2

FOR i=0 to ('$(numRow)'-1);

//let vPort=peek('PortLoop',$(i),'Loop1');
let vBD=peek('BDLoop',$(i),'Loop1');
let vAD=peek('AnLoop',$(i),'Loop1');

if len('$(vAD)')=0 then
EXIT Sub;

ELSE
//
MaxLoop:
LOAD ACCT_SYSTEM_PORTF_NO_PERF,
$(vAD) as ANALYSIS_DATE,
BUSINESS_DATE_PERF,
max([Comp PF Return]) as MaxCompPF,
max([Comp BM Return]) as MaxCompBM,
max([Comp Active Return]) as MaxCompAct
Resident PERF_TEMP Where ANALYSIS_DATE<=$(vAD) and BUSINESS_DATE_PERF='$(vBD)' Group By ACCT_SYSTEM_PORTF_NO_PERF,BUSINESS_DATE_PERF; //and ACCT_SYSTEM_PORTF_NO_PERF='$(vPort)'

ML1:

LOAD ACCT_SYSTEM_PORTF_NO_PERF,
ANALYSIS_DATE,
BUSINESS_DATE_PERF,
[Comp PF Return],
[Comp BM Return],
[Comp Active Return]

Resident PERF_TEMP Where ANALYSIS_DATE=$(vAD) and BUSINESS_DATE_PERF='$(vBD)';//and ACCT_SYSTEM_PORTF_NO_PERF='$(vPort)

Left Join (ML1) LOAD * Resident MaxLoop;
DROP Table MaxLoop;

The code is working fine in QV version 12.1 but not working in QV version 12.4 and we have a same data sets.

When I tried num with Peek it return it is not functioning properly.

could you please assist me?

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 09:16:07 GMT

In general there was no change on logic and syntax and therefore it should further work. Therefore I assume that the included data respectively their interpreting have changed. The interpretation depends on the interpretation-variables at the beginning of the script respectively if they aren't specified on the OS regional settings. Also the load-order could have an impact.

Because of the fact that you mentioned that num(peek()) returned not a value hints that peek() returned a string-value which couldn't num() to format. This might be solved within the variable-assigning with num#() which could convert a string but IMO better would be if you check the data and their interpretation already by loading them before you decide in which way you adjust it. I wouldn't try to check such things within a loop-logic else just loading the data in tables within the UI. Beside any formatting the value-typ of numeric or string is easily visible within the right/left aligning of the values.

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 10:46:46 GMT

Hi Marcus,

I think there are changes in the interpretation variables. But we have created the new app so it should be as per the system defined format and there no manual changes from our side.

At the start of the script,

Below are the snaps for the two apps,

12.1 (Where the script runs successfully)

12.4(where script fails)

But I don't know but nothing is working.

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 11:12:13 GMT

The interpretation-variables for dates look equally between both releases. How does it look like if you loads the data directly without any loop or clauses like above mentioned. Any differences between the releases?

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 11:18:41 GMT

Hi Marcus,

Without any loop, there are no issues. But with loops it is throwing an error as mentioned above.

Apart from this, if I can run the data model layer as it is by using the already created QVd in 12.1 in that case also my results are not matching.

This is weird and the most pressing issue. Unfortunately, on the web there is no available information related to this.

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 11:40:20 GMT

Take a look within the document-log. Is the loop running at least once? Where did it break? How are the various variables evaluated until it breaks?

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 12:04:01 GMT

Hi Marcus,

PFA document log.

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 12:12:41 GMT

There are at least some mistakes by calling variables, for example:

...

FOR i=0 to ($(numRow)-1);
...

'$(vAD)' as ANALYSIS_DATE,
...
Resident PERF_TEMP
Where ANALYSIS_DATE<='$(vAD)' and BUSINESS_DATE_PERF='$(vBD)'
Group By ACCT_SYSTEM_PORTF_NO_PERF,BUSINESS_DATE_PERF;
...

with too much respectively missing quotes. Number should be called without quotes and strings with quotes.

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 12:48:15 GMT

Hi Marcus,

1. We have the exact same code for both of the versions.

2. I already tried as per the above suggestions but nothing works.

I am attaching the log where the script runs successfully.

The only difference I observed that the vAD and vBD dates ate in the numeric formats in the 12.1 which is not appearing in 12.4.

also, whenever I am trying to achieve the above using the num function, peek function returns more than one value which is again not as per the need so our results are not matching.

Even if I can run the data model layer as it is based on the already created QVd's in the version 12.1 then also some values are missing which is weird behavior.

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 12:59:00 GMT

You need to go to the appropriate load-steps which generate these data to find the cause why they are treated differently. Means you load these data resident from any table and even these source-data might have another load in which the interpretation could have changed.

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 15:18:23 GMT

Hi Marcus,

The differences are as per the below.

Version 12.1 where script runs successfully.

Version 12.4 where script fails ->

Num with peek is not the solution for this. The behavior is again different.

I am pretty sure, this issue is related to different versions. Ans the issue whatever we have in QV version 12.4 the same appears in Qlik sense.

I think nothing to do anything in the code but we need some assistance from people like you or from the qlik.

Thanks

Thanks.

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 15:47:06 GMT

The difference is quite clear. In 12.1 it's a date without a formatting and in 12.4 it's a formatted timestamp whereby it's not obvious it's a string or a dual-value (means string-value + numeric-value)?

This means your issue happens in beforehand - not within your loop respectively the error there is an aftereffect. Therefore take a look on all load-steps before and anywhere there you will find that the data will be interpreted differently.

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 15:58:03 GMT

Hi Marcus,

Yes exactly, the issue is because of interpretation of the data which happened differently in the both versions.
But I am not getting how to interpret the data in the same way how it was in the version 12.1?

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Mon, 28 Mar 2022 16:13:15 GMT

I suggest to start at the beginning of the ETL process. This may be not these application else some applications before which the data generate within qvd's or from where the data are loaded.

Of course you may tweak the issue in the step where you load the data here or assigning the variables with something like:

floor(timestamp#(YourTimestampField, 'FormatPattern'))

but then you may run in other cases in similar issues, too. It's recommended to prepare all data as soon as possible - means by fetching the raw-data - not to need to do such adjustments multiple times on various places within the script and/or the UI.

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

deep2021 — Mon, 28 Mar 2022 16:54:00 GMT

Hi Marcus,

Currently, I am using the same QVD for both of the places.

QVDs that are generated in version 12.1, that I am using in 12.4.

Do I need to do anything related to the same.

Is there are issues if I can use the QVD's that are generated in the lower version?

Thanks

Re: Issue with the Peek function in qlikview version 12.40.20400.0

marcus_sommer — Tue, 29 Mar 2022 05:33:14 GMT

I think there are no issues with the qvd creation or usage. But anywhere within your load-chain is anything different. It might be not the qvd's else another step. There are various possibilities why certain data might be interpreted differently - but that the data within your older release are dates and within the newer one are timestamps (independent from the format-stuff) means that the values itself aren't identically.

Therefore I would like to repeat my suggestion from above to go step by step through your load-chain to see where will be which data loaded and how they are loaded/interpreted. It's not a special approach else a common method to validate data - and quite often it's useful not to do everything within the original chain else to pick the parts separately within another qvw. Important is to make this kind of systematically - starting completely at the beginning or reverse from the end or by larger chains also to jump in the middle and from the middle to the middle of the middle - what happens, does the data look like expected or not. Usually it doesn't take long to find the place where something unexpected happens ...

- Marcus

Re: Issue with the Peek function in qlikview version 12.40.20400.0

stevedark — Tue, 29 Mar 2022 09:37:15 GMT

Hi @deep2021

Looking at the original screenshot of your error, it would appear that the single quotes are missing from the ANALYSIS_DATE date in the WHERE statement.

I think you need to add them in here:

Resident PERF_TEMP Where ANALYSIS_DATE='$(vAD)' and BUSINESS_DATE_PERF='$(vBD)';//and ACCT_SYSTEM_PORTF_NO_PERF='$(vPort)

Hope that helps.

Steve