Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
olivierrobin
Specialist III
Specialist III

problem with transfer state in qlikview

Hello,
I have a strange behavior with document chaining
You will find attached 2 applications:
Doc1 is the calling one in which selections are made
Doc2 is the called one in which selections should be transmitted
Some of the numerous strange things I have :
If I select "M vs M-1" in field Vision in Doc 1, it results in "Mensuel" selected in Doc2
If I select "Cumul annuel" in field Vision in Doc 1, it is not selected in Doc2 (despite the fact this value exists in the field in Doc2)
if I select a value in "Unite GL" in Doc1, it is selected in Doc2 if it exists in Doc2 (that seems normal)
if I select "12/2018" in field Vision in Doc1, it results in "01/2019" selected in Doc2
if I select "01/2019" in field Vision in Doc1, it is not selected in Doc2 (despite the fact this value exists in the field in Doc2)
if I select "06/2018" in field Vision in Doc1, it is correctly selected in Doc2

we are using QV 12.10.20000.0 SR2
the applications are intended to be used with IE 11 in Ajax Mode

Labels (3)
1 Solution

Accepted Solutions
olivierrobin
Specialist III
Specialist III
Author

for information, i think this because Periode and Vision are built with dual() function and that if the string values are the same is both models, numeric values are different (for value Cumul Annuel and 12/2018) and so it is impossible to match the values between the 2 applications

View solution in original post

3 Replies
olivierrobin
Specialist III
Specialist III
Author

for information, i think this because Periode and Vision are built with dual() function and that if the string values are the same is both models, numeric values are different (for value Cumul Annuel and 12/2018) and so it is impossible to match the values between the 2 applications

Brett_Bleess
Former Employee
Former Employee

I was able to find a defect QV-10092, that was fixed in SR4 and later releases of 12.10 track, which related to transfer state not working in document chaining.  Is there any chance you can update your environment to try later SR here?  The latest 12.10 SR is SR10, build 12.10.20800.  That would rule out that bug if you still see things in the new SR.  The other option would be to test 12.20 SR8, latest build there, or 12.30 SR1, but that last one is still fairly new, so would understand if you were hesitant to jump to that.  Hope this helps a bit.  I was going to try to test things, but I saw you did not have buttons with the actions configured etc. in your sample apps, so could not take the time to try to set that all up.  If you can do that and reattach, I would be happy to see if I can replicate things at that point.

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
olivierrobin
Specialist III
Specialist III
Author

hello

thanks for your answer

but I can'it install a new version of qv

in the attached qv of the original post, in Doc1, you have in the center of the form a blue text box containing an action to lok to Doc2

 

If you  look at my reply to my own post, you will see that the problem was caused by the dual() function used to compute the 2 fields Vision and Periode.

As the dual() didn't return the same numeric value for the same string, the values were not correctly passed between the 2 applications.