<?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: REST Connection Data Source - How to handle incremental load? in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1555565#M3687</link>
    <description>&lt;DIV class="main-content-container"&gt;&lt;DIV class="main-content"&gt;&lt;DIV class="yk-container"&gt;&lt;DIV class="zindex-t1 column-container yk-row"&gt;&lt;DIV class="yk-col-sm-offset-5 yk-col-md-offset-6 yk-col-lg-offset-7 page-content yk-container pushed-down"&gt;&lt;DIV&gt;&lt;DIV class="page-content-container yk-col-sm-19 yk-col-md-24 yk-col-lg-26 yk-center-block"&gt;&lt;DIV class="yk-row"&gt;&lt;DIV class="column-two-left yk-col-sm-13 yk-col-md-17 yk-col-lg-19"&gt;&lt;DIV class="yj-thread-list yj-list-wrapper"&gt;&lt;DIV class="yj-thread-list--body yj-list-container"&gt;&lt;DIV class="yj-thread-list--content-container"&gt;&lt;DIV class="indicators-treatment yj-message-list-item yj-thread-starter is-not-translated"&gt;&lt;DIV class="yj-message-list-item--message-container yj-message-container"&gt;&lt;DIV class="yj-message-list-item--body yj-message-body"&gt;&lt;DIV class="yj-message-body"&gt;&lt;SPAN class="yj-message-list-item--body-message yj-message"&gt;&lt;SPAN class="remaining-body"&gt;Hello Dwforest,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="yj-message-body"&gt;&lt;SPAN class="yj-message-list-item--body-message yj-message"&gt;&lt;SPAN class="remaining-body"&gt;Let me explain the scenario a bit more clearly. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="yj-message-body"&gt;&lt;SPAN class="yj-message-list-item--body-message yj-message"&gt;&lt;SPAN class="remaining-body"&gt;We have a data store. It has a REST API using which we can extract data in JSON format. The API has pagination by which we can figure out the new data available in that data store. Pagination is explained below with dummy REST calls.&lt;BR /&gt;API call #1 - &lt;A title="https://datastore/data/get?start=1&amp;amp;end=5000" href="https://datastore/data/get?start=1&amp;amp;end=5000" target="_blank" rel="nofollow noopener noreferrer"&gt;https://datastore/data/get?start=1&amp;amp;end=5000&lt;/A&gt; &amp;lt;= this REST API call will provide first 5000 data items from data store.&lt;BR /&gt;API call #2 - &lt;A title="https://datastore/data/get?start=5001&amp;amp;end=6000" href="https://datastore/data/get?start=5001&amp;amp;end=6000" target="_blank" rel="nofollow noopener noreferrer"&gt;https://datastore/data/get?start=5001&amp;amp;end=6000&lt;/A&gt; &amp;lt;= this REST API all provides the 999 newly added data items.&lt;BR /&gt;We need Qlikview to first consume data from url #1 and then every day there will be incremental load by url #2.&lt;BR /&gt;Looking forward for expert opinion on what should be the implementation road map for this scenario in Qlikview or QlikSense.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 12 Mar 2019 17:03:24 GMT</pubDate>
    <dc:creator>maxlin04</dc:creator>
    <dc:date>2019-03-12T17:03:24Z</dc:date>
    <item>
      <title>REST Connection Data Source - How to handle incremental load?</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1554305#M3676</link>
      <description>&lt;P&gt;Can anybody please suggest me a way to handle incremental load in Qliksense while using REST connector?&lt;BR /&gt;Present scenario is - We can fetch data from a REST API. The REST api supports pagination by which we can track the delta for a particular time window. We are planning to get this incremental load periodically and update out Qliksense data store without the hassle of loading the whole data set every time. Can anybody please help me here ?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Dec 2021 19:00:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1554305#M3676</guid>
      <dc:creator>maxlin04</dc:creator>
      <dc:date>2021-12-23T19:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: REST Connection Data Source - How to handle incremental load?</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1554397#M3677</link>
      <description>if the REST source data has a "create/update date", why not just limit it to new records; it would be challenging to get specific dates to be within a certain page range unless your data is very consistent.&lt;BR /&gt;The date parameter can be added to the REST in the Query Parameters of the connection dialog.</description>
      <pubDate>Fri, 08 Mar 2019 18:20:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1554397#M3677</guid>
      <dc:creator>dwforest</dc:creator>
      <dc:date>2019-03-08T18:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: REST Connection Data Source - How to handle incremental load?</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1555565#M3687</link>
      <description>&lt;DIV class="main-content-container"&gt;&lt;DIV class="main-content"&gt;&lt;DIV class="yk-container"&gt;&lt;DIV class="zindex-t1 column-container yk-row"&gt;&lt;DIV class="yk-col-sm-offset-5 yk-col-md-offset-6 yk-col-lg-offset-7 page-content yk-container pushed-down"&gt;&lt;DIV&gt;&lt;DIV class="page-content-container yk-col-sm-19 yk-col-md-24 yk-col-lg-26 yk-center-block"&gt;&lt;DIV class="yk-row"&gt;&lt;DIV class="column-two-left yk-col-sm-13 yk-col-md-17 yk-col-lg-19"&gt;&lt;DIV class="yj-thread-list yj-list-wrapper"&gt;&lt;DIV class="yj-thread-list--body yj-list-container"&gt;&lt;DIV class="yj-thread-list--content-container"&gt;&lt;DIV class="indicators-treatment yj-message-list-item yj-thread-starter is-not-translated"&gt;&lt;DIV class="yj-message-list-item--message-container yj-message-container"&gt;&lt;DIV class="yj-message-list-item--body yj-message-body"&gt;&lt;DIV class="yj-message-body"&gt;&lt;SPAN class="yj-message-list-item--body-message yj-message"&gt;&lt;SPAN class="remaining-body"&gt;Hello Dwforest,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="yj-message-body"&gt;&lt;SPAN class="yj-message-list-item--body-message yj-message"&gt;&lt;SPAN class="remaining-body"&gt;Let me explain the scenario a bit more clearly. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="yj-message-body"&gt;&lt;SPAN class="yj-message-list-item--body-message yj-message"&gt;&lt;SPAN class="remaining-body"&gt;We have a data store. It has a REST API using which we can extract data in JSON format. The API has pagination by which we can figure out the new data available in that data store. Pagination is explained below with dummy REST calls.&lt;BR /&gt;API call #1 - &lt;A title="https://datastore/data/get?start=1&amp;amp;end=5000" href="https://datastore/data/get?start=1&amp;amp;end=5000" target="_blank" rel="nofollow noopener noreferrer"&gt;https://datastore/data/get?start=1&amp;amp;end=5000&lt;/A&gt; &amp;lt;= this REST API call will provide first 5000 data items from data store.&lt;BR /&gt;API call #2 - &lt;A title="https://datastore/data/get?start=5001&amp;amp;end=6000" href="https://datastore/data/get?start=5001&amp;amp;end=6000" target="_blank" rel="nofollow noopener noreferrer"&gt;https://datastore/data/get?start=5001&amp;amp;end=6000&lt;/A&gt; &amp;lt;= this REST API all provides the 999 newly added data items.&lt;BR /&gt;We need Qlikview to first consume data from url #1 and then every day there will be incremental load by url #2.&lt;BR /&gt;Looking forward for expert opinion on what should be the implementation road map for this scenario in Qlikview or QlikSense.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 12 Mar 2019 17:03:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/REST-Connection-Data-Source-How-to-handle-incremental-load/m-p/1555565#M3687</guid>
      <dc:creator>maxlin04</dc:creator>
      <dc:date>2019-03-12T17:03:24Z</dc:date>
    </item>
  </channel>
</rss>

