<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Refresh the app only for updated tab in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Refresh-the-app-only-for-updated-tab/m-p/2541576#M109355</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;I am looking to optimize and automate our current data refresh process for the Products_Query workflow. Currently, the process requires significant manual intervention, and I’d like to move toward a more dynamic, automated solution in QlikView.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Current Workflow (Manual)&lt;/STRONG&gt;&lt;BR /&gt;Centralized File: We use a single Excel file (Products_Query) with one tab.&lt;/P&gt;
&lt;P&gt;Manual Updates: Whenever any of our 150 SQL queries need updating, I manually paste the new query into this sheet.&lt;/P&gt;
&lt;P&gt;Manual Union: If multiple queries are updated, I manually perform a SQL Union within the Excel cell/tab.&lt;/P&gt;
&lt;P&gt;Load: QlikView reads this consolidated query to fetch sales data from AWS and appends it to our historical QVD.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Proposed Workflow (Automated)&lt;/STRONG&gt;&lt;BR /&gt;I want to eliminate the manual "copy-paste-union" steps by implementing the following:&lt;/P&gt;
&lt;P&gt;Multi-Sheet Configuration: Create an Excel file where each of the 150 products has its own dedicated sheet containing its specific SQL query.&lt;/P&gt;
&lt;P&gt;Conditional Execution: On a scheduled daily refresh, QlikView will check if a sheet's SQL text has changed.If changed: QlikView executes that specific SQL against the AWS database and updates the historical QVD. If unchanged: QlikView skips the AWS call for that product to save resources.&lt;/P&gt;
&lt;P&gt;I need your help and welcomes alternate ideas also.&lt;/P&gt;
&lt;P&gt;Thanks in advance,&lt;/P&gt;</description>
    <pubDate>Mon, 26 Jan 2026 19:20:53 GMT</pubDate>
    <dc:creator>Rvr123</dc:creator>
    <dc:date>2026-01-26T19:20:53Z</dc:date>
    <item>
      <title>Refresh the app only for updated tab</title>
      <link>https://community.qlik.com/t5/App-Development/Refresh-the-app-only-for-updated-tab/m-p/2541576#M109355</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;I am looking to optimize and automate our current data refresh process for the Products_Query workflow. Currently, the process requires significant manual intervention, and I’d like to move toward a more dynamic, automated solution in QlikView.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Current Workflow (Manual)&lt;/STRONG&gt;&lt;BR /&gt;Centralized File: We use a single Excel file (Products_Query) with one tab.&lt;/P&gt;
&lt;P&gt;Manual Updates: Whenever any of our 150 SQL queries need updating, I manually paste the new query into this sheet.&lt;/P&gt;
&lt;P&gt;Manual Union: If multiple queries are updated, I manually perform a SQL Union within the Excel cell/tab.&lt;/P&gt;
&lt;P&gt;Load: QlikView reads this consolidated query to fetch sales data from AWS and appends it to our historical QVD.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Proposed Workflow (Automated)&lt;/STRONG&gt;&lt;BR /&gt;I want to eliminate the manual "copy-paste-union" steps by implementing the following:&lt;/P&gt;
&lt;P&gt;Multi-Sheet Configuration: Create an Excel file where each of the 150 products has its own dedicated sheet containing its specific SQL query.&lt;/P&gt;
&lt;P&gt;Conditional Execution: On a scheduled daily refresh, QlikView will check if a sheet's SQL text has changed.If changed: QlikView executes that specific SQL against the AWS database and updates the historical QVD. If unchanged: QlikView skips the AWS call for that product to save resources.&lt;/P&gt;
&lt;P&gt;I need your help and welcomes alternate ideas also.&lt;/P&gt;
&lt;P&gt;Thanks in advance,&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 19:20:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Refresh-the-app-only-for-updated-tab/m-p/2541576#M109355</guid>
      <dc:creator>Rvr123</dc:creator>
      <dc:date>2026-01-26T19:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Refresh the app only for updated tab</title>
      <link>https://community.qlik.com/t5/App-Development/Refresh-the-app-only-for-updated-tab/m-p/2541582#M109356</link>
      <description>&lt;P&gt;This shouldn't be too hard to do, assuming the sheet names are fixed. Separating it into chunks, your algorithm would be something like:&lt;/P&gt;&lt;P&gt;For each tab in tablist&lt;/P&gt;&lt;P&gt;Load current query as text&lt;/P&gt;&lt;P&gt;Check if previous version exists (if it does, we'll have a QVD for it)&lt;/P&gt;&lt;P&gt;If exists, load previous verison and compare them&lt;/P&gt;&lt;P&gt;If identical,&lt;STRONG&gt;&amp;nbsp;stop here and loop to next sheet&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Store current query into QVD named as per the sheet name (e.g. Sheet1_Query)&lt;/P&gt;&lt;P&gt;Run query and store result to QVD based on sheet name (e.g. Sheet1_Data)&lt;/P&gt;&lt;P&gt;Drop result.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Loop 150 time;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Full load: Load 150 QVDs (Some will be new, others will be old because nothing changed)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Feeding this into GPT should give you the exact code, so I'm not including it as it's a tad on the long side.&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could also do this by loading data from QVD if identical and from query if not, but I personally prefer this approach. Either way works, though.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 22:28:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Refresh-the-app-only-for-updated-tab/m-p/2541582#M109356</guid>
      <dc:creator>Or</dc:creator>
      <dc:date>2026-01-26T22:28:27Z</dc:date>
    </item>
  </channel>
</rss>

