Is there a way to do dynamic update in clustered environment?
Unfortunately I can't test this because DEV and QA are not clustered.
We have a load balanced clustered environment for Qlikview in UAT and Production.
I am told we simply cannot use dynamic update on a clustered server, but I am not sure what that means and wonder if I then export macro and reload if it would work.
So the real question is what happens when you have a load balanced Qlikview environment and try and do Dynamic Update?
Does it:
A) Do nothing
B) kind of work inserting the record just into the node that is being used?
If it's B) then I might be able to work with that if I can then export the table and do either a partial reload or EDX reload.
My first question is why you need Dynamic Update? Do you already use it in your production environment? Just so that I understand the business need behind it.
In a server deployment a end-user will not be able to trigger a reload from the client. So your macro will not work in that scenario. An EDX trigger would be the only option externally trigger a reload. What do you expect to happen if two users trigger this simultaneously? I think it might be hard to realize such a scenario.
I very rarely hear that Dynamic Update is being used by customers. Commonly the business needs are solved with partial reload or Direct Discovery. This is likely due to limitation I mentioned above.
The business need is for to allow the users to enter notes.
Dynamic update even with an EDX reload offers a nicer way to accomplish this than using Input fields.
Te built in Notes feature in Qlikview is too limited.
As I see it the need could potentially be met with of the following:
* Dynamic Update - if it can work in clustered environment
* Input fields
* 3rd Party Solution like Insight which I am looking into. That's a full collaboration solution and overkill but I'm not happy with how the input fields work.
Regardless of if we use Dynamic Update or Input fields we run the risk of two users editing/adding notes for the same record at the same time, while the DBA in me detests that it is considered an acceptable margin of error in this case.
If we were not in a clustered environment I would lean towards Dynamic Update even if it required the use of an EDX reload.
The other issue is I want a consistent solution across all dashboards and Input fields would be easy to implement into mine but some of the legacy dashboards are designed in a manner that would make it more difficult to use input fields. .
Honestly, I do not have a direct answer to your question. I'll have to take a look at any documentation we have and see if I can find a official answer for you.
