<?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: Best Practice - Report delivery in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2163769#M94493</link>
    <description>&lt;P&gt;Thanks! Will definitely check it out&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jan 2024 09:53:17 GMT</pubDate>
    <dc:creator>bchip01</dc:creator>
    <dc:date>2024-01-22T09:53:17Z</dc:date>
    <item>
      <title>Best Practice - Report delivery</title>
      <link>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2162991#M94418</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;
&lt;P&gt;I was just wondering what are the thoughts on the forum for best practice with report delivery.&amp;nbsp; In the past with Qlik sense/view one could deliver a report on a file server by using STORE txt. Then N-Printing came along and helped further with this process.&lt;/P&gt;
&lt;P&gt;My thoughts are more with Qlik Cloud/SaaS.&amp;nbsp; Nprinting has now fallen away with Cloud and Automations can be used, however Automations have a major limitation of 100,000 cells (not rows) which really means only very small reports can be sent to a Google sheet or a Dropbox file.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I connect to a straight table with &amp;gt; 100k cells the automations dont work.&lt;/P&gt;
&lt;P&gt;If I can get the table to show (with more than 100k cells) through looping (and filter selections) in the automation then it goes from a few seconds to&amp;nbsp; a long time to publish a report, which is incredibly slow for the actual size.&lt;/P&gt;
&lt;P&gt;So at the moment I'm looking at using the STORE for a larger report into a dropbox/google cloud point.&amp;nbsp; I was just wondering what everyone else uses, and if I have missed anything.&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 18:14:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2162991#M94418</guid>
      <dc:creator>bchip01</dc:creator>
      <dc:date>2024-01-18T18:14:11Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice - Report delivery</title>
      <link>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2163704#M94492</link>
      <description>&lt;P&gt;Hi, have you tried tabular reports? I haven't had time to test it in a real production environment yet, but it looks like it has a lot of potential.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=0g3v0ciaiiM" target="_blank"&gt;https://www.youtube.com/watch?v=0g3v0ciaiiM&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=0V5JJjwF3bw" target="_blank"&gt;https://www.youtube.com/watch?v=0V5JJjwF3bw&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 08:20:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2163704#M94492</guid>
      <dc:creator>rubenmarin</dc:creator>
      <dc:date>2024-01-22T08:20:46Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice - Report delivery</title>
      <link>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2163769#M94493</link>
      <description>&lt;P&gt;Thanks! Will definitely check it out&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 09:53:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Best-Practice-Report-delivery/m-p/2163769#M94493</guid>
      <dc:creator>bchip01</dc:creator>
      <dc:date>2024-01-22T09:53:17Z</dc:date>
    </item>
  </channel>
</rss>

