<?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: Large Dataset Wide and Long Table Load Times Issue in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443801#M97537</link>
    <description>&lt;P&gt;Transform your data to qvd or parquet format.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It may reduce the time&lt;/P&gt;</description>
    <pubDate>Tue, 23 Apr 2024 08:00:05 GMT</pubDate>
    <dc:creator>CHRIS_Singa</dc:creator>
    <dc:date>2024-04-23T08:00:05Z</dc:date>
    <item>
      <title>Large Dataset Wide and Long Table Load Times Issue</title>
      <link>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443692#M97527</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have a data set of 1.3 million rows. For a lot of the visuals I require a long table so when i create a long table it produces 153 million rows. The widgets have a hard time loading that much data especially when the widget is using the long table. the long table gives me what im looking for in the visuals but the widget loading is really bad, Is there any other options that has the same functionality of the long table?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 23:10:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443692#M97527</guid>
      <dc:creator>Asuod_</dc:creator>
      <dc:date>2024-04-22T23:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: Large Dataset Wide and Long Table Load Times Issue</title>
      <link>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443794#M97536</link>
      <description>&lt;P&gt;A well build data-model + UI have not mandatory a problem with 153 M of records. Please elaborate in more details how data-model + data + UI + expression are look like.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 07:49:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443794#M97536</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2024-04-23T07:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: Large Dataset Wide and Long Table Load Times Issue</title>
      <link>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443801#M97537</link>
      <description>&lt;P&gt;Transform your data to qvd or parquet format.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It may reduce the time&lt;/P&gt;</description>
      <pubDate>Tue, 23 Apr 2024 08:00:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Large-Dataset-Wide-and-Long-Table-Load-Times-Issue/m-p/2443801#M97537</guid>
      <dc:creator>CHRIS_Singa</dc:creator>
      <dc:date>2024-04-23T08:00:05Z</dc:date>
    </item>
  </channel>
</rss>

