https://community.qlik.com/t5/Official-Support-Articles/QlikView-Dynamic-Update-intended-use-and-pros-and-cons/ta-p/1710881 <P>There is a setting in the QlikView Management Console(QMC) &gt; QlikView Server &gt; Security tab for Allow Dynamic Data Update.&nbsp; &nbsp;The Pros and Cons for this feature and whether it is the best method for updating&nbsp;data in a currently loaded document will be discussed.</P> <P>Rather than focusing on Dynamic Update, Qlik is embracing <STRONG>On-Demand Application Generation (ODAG) </STRONG>as a Big Data methodology, which provides users with a "shopping list" experience allowing a particular subset of data to interactively populate the application.&nbsp; This provides full QlikView/QlikSense functionality on a latent subset that is hosted in memory.&nbsp;</P> <P><STRONG>Related Content:</STRONG></P> <UL> <LI><A href="https://help.qlik.com/en-US/sense/June2020/Subsystems/Hub/Content/Sense_Hub/LoadData/using-OnDemand-apps.htm" target="_blank" rel="noopener">On-demand Apps (Qlik Sense)</A></LI> <LI><A href="https://help.qlik.com/en-US/sense/June2020/Subsystems/Hub/Content/Sense_Hub/DataSource/Manage-big-data.htm" target="_blank" rel="noopener">Managing big data with on-demand apps (Qlik Sense)</A>&nbsp;</LI> <LI>See attached Big Data and ODAG pptx and .mp4</LI> </UL> <P>&nbsp;</P> <H3><STRONG>Intended Use of Dynamic Update:</STRONG></H3> <P>&nbsp;</P> <DIV>The intended usage of Dynamic Update allows a <STRONG>QlikView Administrator</STRONG> to:</DIV> <UL> <LI>feed limited amounts of data into a QlikView document</LI> <LI>from a single source&nbsp;</LI> <LI>without running a reload of the document</LI> <LI>Dynamic Update is NOT supported in a QlikView Server clustered environment</LI> </UL> <P>&nbsp;</P> <H3><SPAN><SPAN><STRONG>PROs</STRONG>:&nbsp;</SPAN></SPAN></H3> <P>&nbsp;</P> <P><SPAN><SPAN>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.</SPAN></SPAN></P> <P>&nbsp;</P> <H3><STRONG>CONs:</STRONG></H3> <P>&nbsp;</P> <UL> <LI>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.</LI> <LI>The users must be a member of the QlikView Administrators local security group on the QlikView Server.</LI> <LI>It is recommended to disable the Allow Dynamic Data Update feature, since it can be resource intensive.</LI> <LI>The Allow Dynamic Data Update feature is not supported in a clustered QlikView Server (QVS) environment</LI> </UL> <P><BR /><BR /></P> <P><BR />&nbsp;</P> Mon, 24 Aug 2020 06:14:14 GMT Sonja_Bauernfeind 2020-08-24T06:14:14Z https://community.qlik.com/t5/Official-Support-Articles/QlikView-Dynamic-Update-intended-use-and-pros-and-cons/ta-p/1710881 <P>There is a setting in the QlikView Management Console(QMC) &gt; QlikView Server &gt; Security tab for Allow Dynamic Data Update.&nbsp; &nbsp;The Pros and Cons for this feature and whether it is the best method for updating&nbsp;data in a currently loaded document will be discussed.</P> <P>Rather than focusing on Dynamic Update, Qlik is embracing <STRONG>On-Demand Application Generation (ODAG) </STRONG>as a Big Data methodology, which provides users with a "shopping list" experience allowing a particular subset of data to interactively populate the application.&nbsp; This provides full QlikView/QlikSense functionality on a latent subset that is hosted in memory.&nbsp;</P> <P><STRONG>Related Content:</STRONG></P> <UL> <LI><A href="https://help.qlik.com/en-US/sense/June2020/Subsystems/Hub/Content/Sense_Hub/LoadData/using-OnDemand-apps.htm" target="_blank" rel="noopener">On-demand Apps (Qlik Sense)</A></LI> <LI><A href="https://help.qlik.com/en-US/sense/June2020/Subsystems/Hub/Content/Sense_Hub/DataSource/Manage-big-data.htm" target="_blank" rel="noopener">Managing big data with on-demand apps (Qlik Sense)</A>&nbsp;</LI> <LI>See attached Big Data and ODAG pptx and .mp4</LI> </UL> <P>&nbsp;</P> <H3><STRONG>Intended Use of Dynamic Update:</STRONG></H3> <P>&nbsp;</P> <DIV>The intended usage of Dynamic Update allows a <STRONG>QlikView Administrator</STRONG> to:</DIV> <UL> <LI>feed limited amounts of data into a QlikView document</LI> <LI>from a single source&nbsp;</LI> <LI>without running a reload of the document</LI> <LI>Dynamic Update is NOT supported in a QlikView Server clustered environment</LI> </UL> <P>&nbsp;</P> <H3><SPAN><SPAN><STRONG>PROs</STRONG>:&nbsp;</SPAN></SPAN></H3> <P>&nbsp;</P> <P><SPAN><SPAN>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.</SPAN></SPAN></P> <P>&nbsp;</P> <H3><STRONG>CONs:</STRONG></H3> <P>&nbsp;</P> <UL> <LI>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.</LI> <LI>The users must be a member of the QlikView Administrators local security group on the QlikView Server.</LI> <LI>It is recommended to disable the Allow Dynamic Data Update feature, since it can be resource intensive.</LI> <LI>The Allow Dynamic Data Update feature is not supported in a clustered QlikView Server (QVS) environment</LI> </UL> <P><BR /><BR /></P> <P><BR />&nbsp;</P> Mon, 24 Aug 2020 06:14:14 GMT https://community.qlik.com/t5/Official-Support-Articles/QlikView-Dynamic-Update-intended-use-and-pros-and-cons/ta-p/1710881 Sonja_Bauernfeind 2020-08-24T06:14:14Z