<?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: Qlik Sense On-Demand Apps Bindings Limit in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2540993#M109277</link>
    <description>&lt;P&gt;Yes, I totally agree with you, and that's what we've been doing with ODAG.&lt;/P&gt;&lt;P&gt;It's just that recently, users reflected that they wished to further analyze the cluster in another app. The apps were separated in the first place; that's why we tried to explore the possibility of using the features.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jan 2026 08:25:36 GMT</pubDate>
    <dc:creator>JinNgiu</dc:creator>
    <dc:date>2026-01-16T08:25:36Z</dc:date>
    <item>
      <title>Qlik Sense On-Demand Apps Bindings Limit</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539025#M109003</link>
      <description>&lt;P&gt;Dear community,&lt;/P&gt;&lt;P&gt;We have millions rows of data, and we're implementing ODAG to handle it. In certain scenarios, the users want a big cluster of the receipts only, hence we're binding the 'ReceiptID' field for the template app.&lt;/P&gt;&lt;P&gt;However, there's an issue when the receipts selection are more than half a million, the 'odag app generation' is not working after we click it.&lt;/P&gt;&lt;P&gt;We'd be really appreciate it if anyone could provide some advices. Not necessarily only in ODAG method, other methods to handle the passing of plenty selections are welcome too.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jin&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Dec 2025 02:30:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539025#M109003</guid>
      <dc:creator>JinNgiu</dc:creator>
      <dc:date>2025-12-12T02:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense On-Demand Apps Bindings Limit</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539104#M109020</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;You can try like below&amp;nbsp;&lt;/P&gt;&lt;P&gt;Receipts:&lt;/P&gt;&lt;P&gt;LOAD *&lt;/P&gt;&lt;P&gt;FROM source&lt;/P&gt;&lt;P&gt;WHERE ReceiptDate &amp;gt;= '$(vStartDate)'&lt;/P&gt;&lt;P&gt;&amp;nbsp; AND ReceiptDate &amp;lt;= '$(vEndDate)';&lt;/P&gt;</description>
      <pubDate>Fri, 12 Dec 2025 16:42:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539104#M109020</guid>
      <dc:creator>Chanty4u</dc:creator>
      <dc:date>2025-12-12T16:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense On-Demand Apps Bindings Limit</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539169#M109030</link>
      <description>&lt;P&gt;Hi Chanty,&lt;/P&gt;&lt;P&gt;Thanks for reply. The scenario we have is to analyze specific receipts only. Using date where clause will include those receipts that are not needed.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 01:42:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539169#M109030</guid>
      <dc:creator>JinNgiu</dc:creator>
      <dc:date>2025-12-15T01:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense On-Demand Apps Bindings Limit</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539182#M109031</link>
      <description>&lt;P&gt;I don't think ODAG is meant to handle parameter passing for hundreds of thousands of values. Presumably, these values have something else in common - perhaps a time period, perhaps some other dimension - and you can pass that along instead. You're not limited to a single field being passed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 04:40:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2539182#M109031</guid>
      <dc:creator>Or</dc:creator>
      <dc:date>2025-12-15T04:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense On-Demand Apps Bindings Limit</title>
      <link>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2540993#M109277</link>
      <description>&lt;P&gt;Yes, I totally agree with you, and that's what we've been doing with ODAG.&lt;/P&gt;&lt;P&gt;It's just that recently, users reflected that they wished to further analyze the cluster in another app. The apps were separated in the first place; that's why we tried to explore the possibility of using the features.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jan 2026 08:25:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Qlik-Sense-On-Demand-Apps-Bindings-Limit/m-p/2540993#M109277</guid>
      <dc:creator>JinNgiu</dc:creator>
      <dc:date>2026-01-16T08:25:36Z</dc:date>
    </item>
  </channel>
</rss>

