<?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: Document Chaining Vs ODAG in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Document-Chaining-Vs-ODAG/m-p/1684015#M52097</link>
    <description>&lt;P&gt;You can possibly achieve document chaining using ODAG, however I would say that is neither the best way nor ODAG is meant for that. ODAG is meant for big data handling. You can achieve document chaining in ways, like:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Sense-Documents-Videos/App-integration-API-simplify-analysis-of-large-data-volumes/ta-p/1492781" target="_self"&gt;Navigation link/ App Inetgration API&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Sense-Documents-Videos/Document-Chaining-in-Qlik-Sense/ta-p/1495402/show-comments/true" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Sense-Documents-Videos/Document-Chaining-in-Qlik-Sense/ta-p/1495402/show-comments/true&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Thu, 12 Mar 2020 07:10:45 GMT</pubDate>
    <dc:creator>tresB</dc:creator>
    <dc:date>2020-03-12T07:10:45Z</dc:date>
    <item>
      <title>Document Chaining Vs ODAG</title>
      <link>https://community.qlik.com/t5/App-Development/Document-Chaining-Vs-ODAG/m-p/1683587#M52049</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a few questions in regrard to ODAG and Document Chaining:&lt;/P&gt;&lt;P&gt;1. Is ODAG the way to achieve Document Chaining in qliksense; if not how do we achieve Document Chaining in Qlik Sense&lt;/P&gt;&lt;P&gt;2. Are ODAG and Document Chaining different from each other ; if yes what are the differences&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/28684"&gt;@kaushiknsolanki&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/25001"&gt;@Vegar&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/22949"&gt;@tresB&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Mar 2020 05:50:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Document-Chaining-Vs-ODAG/m-p/1683587#M52049</guid>
      <dc:creator>anushree1</dc:creator>
      <dc:date>2020-03-12T05:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: Document Chaining Vs ODAG</title>
      <link>https://community.qlik.com/t5/App-Development/Document-Chaining-Vs-ODAG/m-p/1684015#M52097</link>
      <description>&lt;P&gt;You can possibly achieve document chaining using ODAG, however I would say that is neither the best way nor ODAG is meant for that. ODAG is meant for big data handling. You can achieve document chaining in ways, like:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Sense-Documents-Videos/App-integration-API-simplify-analysis-of-large-data-volumes/ta-p/1492781" target="_self"&gt;Navigation link/ App Inetgration API&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Sense-Documents-Videos/Document-Chaining-in-Qlik-Sense/ta-p/1495402/show-comments/true" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Sense-Documents-Videos/Document-Chaining-in-Qlik-Sense/ta-p/1495402/show-comments/true&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 12 Mar 2020 07:10:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Document-Chaining-Vs-ODAG/m-p/1684015#M52097</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2020-03-12T07:10:45Z</dc:date>
    </item>
  </channel>
</rss>

