<?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: Limitations in text fields in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Limitations-in-text-fields/m-p/539718#M1234705</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds like it's just a javascript/browser limitation.&amp;nbsp; You're trying to plot way too many points on the map.&amp;nbsp; Even if you're only trying to show 4 or 5 regions, each long/lat point that it takes to plot that region increases the load on javascript and the map.&amp;nbsp; This is why when there's a need for a large amount of points, you probably need to start looking at a server side mapping solution.&lt;/P&gt;&lt;P&gt;On the other hand, if all you're wanting to do is outline some countries, you could switch to using the svgReader extension.&amp;nbsp; If you want to also plot points, you could maybe find a less precise set of boundary data.&amp;nbsp; If it's using that many points to outline a region, it's probably being too exact in its drawing of boundaries.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Dec 2013 15:59:52 GMT</pubDate>
    <dc:creator>Brian_Munz</dc:creator>
    <dc:date>2013-12-06T15:59:52Z</dc:date>
    <item>
      <title>Limitations in text fields</title>
      <link>https://community.qlik.com/t5/QlikView/Limitations-in-text-fields/m-p/539717#M1234704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am facing a problem in connection with a geo extension, which loads boundaries in form of different points (log/latitudes). When I select a country (reduce data) everything works fine, when I clear the status (=all data) QV crashes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As the field with the boundaries contains up to 15000 digits per location (data row), I guess it could have to do something with some internal limitations in QV. It happens only in web view and in connection with a geo extension.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody has a solution/explanation how to manage this problem? I have tried it with 11.2 SR4 and 11.2 SR5 Beta.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 16:26:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Limitations-in-text-fields/m-p/539717#M1234704</guid>
      <dc:creator>p_noindl</dc:creator>
      <dc:date>2026-01-26T16:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: Limitations in text fields</title>
      <link>https://community.qlik.com/t5/QlikView/Limitations-in-text-fields/m-p/539718#M1234705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds like it's just a javascript/browser limitation.&amp;nbsp; You're trying to plot way too many points on the map.&amp;nbsp; Even if you're only trying to show 4 or 5 regions, each long/lat point that it takes to plot that region increases the load on javascript and the map.&amp;nbsp; This is why when there's a need for a large amount of points, you probably need to start looking at a server side mapping solution.&lt;/P&gt;&lt;P&gt;On the other hand, if all you're wanting to do is outline some countries, you could switch to using the svgReader extension.&amp;nbsp; If you want to also plot points, you could maybe find a less precise set of boundary data.&amp;nbsp; If it's using that many points to outline a region, it's probably being too exact in its drawing of boundaries.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Dec 2013 15:59:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Limitations-in-text-fields/m-p/539718#M1234705</guid>
      <dc:creator>Brian_Munz</dc:creator>
      <dc:date>2013-12-06T15:59:52Z</dc:date>
    </item>
  </channel>
</rss>

