QlikView documentation and resources.
We are a heavy user of QlikView's dynamic update functionality (i.e. DynamicUpdateCommand), and rely on it to create user defined dimension values (I won't go into the process of how users define a new dimension value, only how it is saved).
Dynamic Update is a very powerful QlikView feature since it allows document data updates in real time, which are made available to all QlikView document users. What follows is a list of tips, tricks, and gotchas:
Good luck!
This document was generated from the following discussion: DynamicUpdateCommand: Top 10 Tips, Tricks, and Gotchas
hi,
im not sure if someone have mention it before or of it was fixed, l ast version i checked was 9 sp4
the DynamicUpdateCommand:insert function have a problem inserting values that containe the ";" semicolon cahr.
Mansyno
Hi Jason,
we are facing problem in the use of Dynamic Update in a QV application that require 15 to 20 cuncurrent users on the same document: we are working to optimize the call of Dynamic Update command because at the moment with 3 users connected the document stop the operativity of QV server.
I seems that the Dynamic Update doesn't queue correctly the calls from different users on the same document, so to solve this problem we will probably need to appliy your suggestion to use a message queuing service such as MSMQ.
Shall you send us a few more details how to manage the calls of QV Dynamic Update on MSMQ trigger sevice?
many thanks
Carlo
Hi Jason,
thanks for your comprehensive listing of tips and tricks. I would also like to know, how "MSMQ trigger sevice" can be used. I cannot find good examples or explainations in the internet on that topic.
Can anyone else help me out on that?
Thanks in advance
Matthias
?
Be aware that all field "Selection" triggers and the "AnySelection" trigger will fire each time DynamicUpdateCommand is called. Depending on where the clients are within the document, this can lead to unexpected behaviour. This is one of the biggest "gotchas" I've discovered.
Yes, this is rather annoying side effect. I found that it can be compensated by adding Selection -> Back action immediately after dynamic update action.