<?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 Re: Alternative to on Demand application feature in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Alternative-to-on-Demand-application-feature/m-p/2475576#M100157</link>
    <description>&lt;P&gt;Hi Nilesh,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;just some ideas based on your provided information &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; . &amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Moving some dimensions to qvds , to reduce the load on Big Query and transfer less data to Qlik&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Enrich selection app with additional data to reduce the amount of templates that needs to be generated&lt;/P&gt;
&lt;P&gt;- Analyze the querys , maybe you can build some new in-memory apps to avoid template generation&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- App Chaining&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Switch to direct query. With 1400 Users not the best idea ...&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Aug 2024 15:31:32 GMT</pubDate>
    <dc:creator>Mark_Leifeld</dc:creator>
    <dc:date>2024-08-09T15:31:32Z</dc:date>
    <item>
      <title>Alternative to on Demand application feature</title>
      <link>https://community.qlik.com/t5/App-Development/Alternative-to-on-Demand-application-feature/m-p/2475397#M100139</link>
      <description>&lt;P&gt;Hi Team,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have an application in Qliksense&amp;nbsp; with On -Demand app generation&amp;nbsp; functionality. The application having heavy user base (Daily 1400 users ) and with each user new on demand app gets created and it hits the query in bakcend via template app to get the result set. we have GCP Big Query in backend.&lt;/P&gt;
&lt;P&gt;We are looking for options to move out from On demand app feature.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions on this&amp;nbsp; would be appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Aug 2024 17:05:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Alternative-to-on-Demand-application-feature/m-p/2475397#M100139</guid>
      <dc:creator>Nilesh_999</dc:creator>
      <dc:date>2024-08-08T17:05:15Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to on Demand application feature</title>
      <link>https://community.qlik.com/t5/App-Development/Alternative-to-on-Demand-application-feature/m-p/2475576#M100157</link>
      <description>&lt;P&gt;Hi Nilesh,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;just some ideas based on your provided information &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; . &amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Moving some dimensions to qvds , to reduce the load on Big Query and transfer less data to Qlik&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Enrich selection app with additional data to reduce the amount of templates that needs to be generated&lt;/P&gt;
&lt;P&gt;- Analyze the querys , maybe you can build some new in-memory apps to avoid template generation&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- App Chaining&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Switch to direct query. With 1400 Users not the best idea ...&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 15:31:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Alternative-to-on-Demand-application-feature/m-p/2475576#M100157</guid>
      <dc:creator>Mark_Leifeld</dc:creator>
      <dc:date>2024-08-09T15:31:32Z</dc:date>
    </item>
  </channel>
</rss>

