<?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 Incremental Load of Sense Users from SaaS API in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Incremental-Load-of-Sense-Users-from-SaaS-API/m-p/1808218#M14939</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I seem to be hitting some issues with the API&amp;nbsp;/api/v1/Users.&lt;/P&gt;&lt;P&gt;What I want to do is quite simple, enumerate getting those with the most recent&amp;nbsp;&lt;STRONG&gt;lastUpdated&lt;/STRONG&gt; value first, paging back through 100 at a time to get all users.&lt;/P&gt;&lt;P&gt;Once this has been done I would like to persist this to QVD, so on the next run the latest update time can be retrieved and only as many pages from the users API be pulled until there are changes older than the most recent in the QVD. Once that has happened the QVD can be appended. Classic incremental load.&lt;/P&gt;&lt;P&gt;The API doesn't seem to support this though, as many of the parameters which should be there (according to&amp;nbsp;&lt;A href="https://qlik.dev/apis/rest/users" target="_blank" rel="noopener"&gt;https://qlik.dev/apis/rest/users&lt;/A&gt;) do not seem to be there, and there are some parameters which would be required which are not even in the documentation (&lt;STRONG&gt;changedSince&lt;/STRONG&gt;).&lt;/P&gt;&lt;P&gt;The documentation suggests that &lt;STRONG&gt;?sort=%2dlastUpdated&lt;/STRONG&gt; should work, but it returns an error (&lt;STRONG&gt;?sort=%2dcreated&lt;/STRONG&gt; does work). Using the separate&amp;nbsp;&lt;STRONG&gt;sortBy&lt;/STRONG&gt; and&amp;nbsp;&lt;STRONG&gt;sortOrder&lt;/STRONG&gt; parameters seems to work even less well, a parameter of &lt;STRONG&gt;?sortBy=create&lt;/STRONG&gt; fails.&lt;/P&gt;&lt;P&gt;I'm guessing that I can sort by&amp;nbsp;&lt;STRONG&gt;name&lt;/STRONG&gt; descending and use the&amp;nbsp;&lt;STRONG&gt;endingBefore&lt;/STRONG&gt; after peeking for the&amp;nbsp;&lt;STRONG&gt;id&lt;/STRONG&gt; of the last row of the table. This would be fine for the first pass (providing you don't have more than a page of invites, as I am not sure how they sort) but I can't see how this could then be used for incrementals.&lt;/P&gt;&lt;P&gt;I'm aware that I could use the pagination settings on the API call, but I don't want to be calling the API more than I have to, as this seems wasteful.&lt;/P&gt;&lt;P&gt;Any suggestions would be gratefully received.&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 16 May 2021 17:27:59 GMT</pubDate>
    <dc:creator>stevedark</dc:creator>
    <dc:date>2021-05-16T17:27:59Z</dc:date>
    <item>
      <title>Incremental Load of Sense Users from SaaS API</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Incremental-Load-of-Sense-Users-from-SaaS-API/m-p/1808218#M14939</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I seem to be hitting some issues with the API&amp;nbsp;/api/v1/Users.&lt;/P&gt;&lt;P&gt;What I want to do is quite simple, enumerate getting those with the most recent&amp;nbsp;&lt;STRONG&gt;lastUpdated&lt;/STRONG&gt; value first, paging back through 100 at a time to get all users.&lt;/P&gt;&lt;P&gt;Once this has been done I would like to persist this to QVD, so on the next run the latest update time can be retrieved and only as many pages from the users API be pulled until there are changes older than the most recent in the QVD. Once that has happened the QVD can be appended. Classic incremental load.&lt;/P&gt;&lt;P&gt;The API doesn't seem to support this though, as many of the parameters which should be there (according to&amp;nbsp;&lt;A href="https://qlik.dev/apis/rest/users" target="_blank" rel="noopener"&gt;https://qlik.dev/apis/rest/users&lt;/A&gt;) do not seem to be there, and there are some parameters which would be required which are not even in the documentation (&lt;STRONG&gt;changedSince&lt;/STRONG&gt;).&lt;/P&gt;&lt;P&gt;The documentation suggests that &lt;STRONG&gt;?sort=%2dlastUpdated&lt;/STRONG&gt; should work, but it returns an error (&lt;STRONG&gt;?sort=%2dcreated&lt;/STRONG&gt; does work). Using the separate&amp;nbsp;&lt;STRONG&gt;sortBy&lt;/STRONG&gt; and&amp;nbsp;&lt;STRONG&gt;sortOrder&lt;/STRONG&gt; parameters seems to work even less well, a parameter of &lt;STRONG&gt;?sortBy=create&lt;/STRONG&gt; fails.&lt;/P&gt;&lt;P&gt;I'm guessing that I can sort by&amp;nbsp;&lt;STRONG&gt;name&lt;/STRONG&gt; descending and use the&amp;nbsp;&lt;STRONG&gt;endingBefore&lt;/STRONG&gt; after peeking for the&amp;nbsp;&lt;STRONG&gt;id&lt;/STRONG&gt; of the last row of the table. This would be fine for the first pass (providing you don't have more than a page of invites, as I am not sure how they sort) but I can't see how this could then be used for incrementals.&lt;/P&gt;&lt;P&gt;I'm aware that I could use the pagination settings on the API call, but I don't want to be calling the API more than I have to, as this seems wasteful.&lt;/P&gt;&lt;P&gt;Any suggestions would be gratefully received.&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 16 May 2021 17:27:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Incremental-Load-of-Sense-Users-from-SaaS-API/m-p/1808218#M14939</guid>
      <dc:creator>stevedark</dc:creator>
      <dc:date>2021-05-16T17:27:59Z</dc:date>
    </item>
  </channel>
</rss>

