Document Chaining occasionally not passing DocumentName variable in ACCESPOINT.

[bmac1]

Hello!

At my company we are seeing an issue with our QV applications where DocumentChaining will sometimes fail, returning a 'Failed to open document, file not found.'

When you go from APP1 to APP2, we use the transfer state option to transfer the value of the APP1 DocumentName() to APP2, so that the user can then return to APP1 with an Open Qlikview Document action.

The problem is, it seems this variable sometimes does not get transferred from APP1 to APP2, resulting in a null variable value in APP2.

Both apps have the variable stored in the variable editor and are in the same path. It also works flawlessy in Desktop Client.

We are using APRIL 2020 SR3 QV version, is anyone aware of any bug with this version causing variables not to be transferred via document chaining and transfer state option? Does anybody know of a workaround?

[David_Friend]

Hi @bmac1 not sure about that issue, however wanted to point out that version is 4 years old, I'd suggest upgrading to a modern version, and see if the issue persists...

[marcus_sommer · Accepted solution]

Qlik is extremely multi-threaded and working much with cached values. This means each user-interaction might be distributed into n threads which are parallel processed and depending on the workload they may finish in a random order and without mandatory waiting on each other. 

Therefore any required dependencies between the threads might be not fulfilled each time. It happens often by adding multiple actions to a single trigger but also by combining selections and/or variables and/or bookmarks (not to forget session recovery) and/or mixing internal + external measurements it may occur.

Beside the above you may to consider to move the variable-value into a field-logic and loading documentname() within an island-table and grabbing then the value from there.