There is a setting in the QlikView Management Console(QMC) > QlikView Server > Security tab for Allow Dynamic Data Update. The Pros and Cons for this feature and whether it is the best method for updating data in a currently loaded document will be discussed.
Rather than focusing on Dynamic Update, Qlik is embracing On-Demand Application Generation (ODAG) as a Big Data methodology, which provides users with a "shopping list" experience allowing a particular subset of data to interactively populate the application. This provides full QlikView/QlikSense functionality on a latent subset that is hosted in memory.
Related Content:
Intended Use of Dynamic Update:
The intended usage of Dynamic Update allows a QlikView Administrator to:
- feed limited amounts of data into a QlikView document
- from a single source
- without running a reload of the document
- Dynamic Update is NOT supported in a QlikView Server clustered environment
PROs:
The Allow Dynamic Data Update was Qlik's original solution to feed limited amounts of 'live' data to a Qlikview document from a single source without running a reload of the document.
CONs:
- The uploaded information is only stored in memory, so any data added or updated using the Allow Dynamic Data Update feature is lost, if a reload of the document occurs during the session.
- The users must be a member of the QlikView Administrators local security group on the QlikView Server.
- It is recommended to disable the Allow Dynamic Data Update feature, since it can be resource intensive.
- The Allow Dynamic Data Update feature is not supported in a clustered QlikView Server (QVS) environment
