<?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: Is it a bad idea to use Qlik Sense API? in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947075#M16973</link>
    <description>&lt;P&gt;If your goal is to reuse the Qlik data tables, a simple and clean method to do this is use the script STORE statement to write the tables as CSV files in your load script.&amp;nbsp; You can then consume the CSV files in other applications.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Rob&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jun 2022 20:00:09 GMT</pubDate>
    <dc:creator>rwunderlich</dc:creator>
    <dc:date>2022-06-22T20:00:09Z</dc:date>
    <item>
      <title>Is it a bad idea to use Qlik Sense API?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947066#M16972</link>
      <description>&lt;P&gt;My organisation is planning to use data from Qlik Sense in other applications.&lt;/P&gt;
&lt;P&gt;Is it a good idea to develop api that connects directly to Qlik engine using #enigmaJs or is there a better solution&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In general is using qlik as a repo a good practice?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 19:41:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947066#M16972</guid>
      <dc:creator>mananshah</dc:creator>
      <dc:date>2022-06-22T19:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Is it a bad idea to use Qlik Sense API?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947075#M16973</link>
      <description>&lt;P&gt;If your goal is to reuse the Qlik data tables, a simple and clean method to do this is use the script STORE statement to write the tables as CSV files in your load script.&amp;nbsp; You can then consume the CSV files in other applications.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Rob&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 20:00:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947075#M16973</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2022-06-22T20:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: Is it a bad idea to use Qlik Sense API?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947100#M16974</link>
      <description>&lt;P&gt;HI,&lt;BR /&gt;I have written API service using ASP .Net and QLIK .net sdk, to connect to qlik, to a model and get data to other services.&lt;/P&gt;
&lt;P&gt;(data that has lots of calcualutions and that the BI developer did in a model, so we didn't want to redo all this calucaltions)&lt;/P&gt;
&lt;P&gt;There is things that u need to consider, like, not opening too many connection to qlik, as u have limit of open connections for the same user.&lt;BR /&gt;You can avoid that by keeping the connection in application variable.&lt;/P&gt;
&lt;P&gt;Or you can cache the data on the API for X hours, so u don't need to connect to qlik each tiem u get a request.&lt;BR /&gt;You also need to be caution when using some filters, in case u access the data with same user on same time.&lt;BR /&gt;&lt;BR /&gt;So taking all considerations u can decide if it will fit your requirements.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 21:47:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Is-it-a-bad-idea-to-use-Qlik-Sense-API/m-p/1947100#M16974</guid>
      <dc:creator>oz_moyal</dc:creator>
      <dc:date>2022-06-22T21:47:15Z</dc:date>
    </item>
  </channel>
</rss>

