<?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: Concatenating two fields, giving rise to App performance issue or slow in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608496#M597357</link>
    <description>&lt;P&gt;Thought that might be the reason, in which case I'd suggest including a delimiter between your two fields in order to avoid possible linking issues.&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;FieldA&lt;/TD&gt;&lt;TD&gt;FieldB&lt;/TD&gt;&lt;TD&gt;FieldA &amp;amp; FieldB as FieldC&lt;/TD&gt;&lt;TD&gt;FieldA &amp;amp; '|' &amp;amp; FieldB as FieldC&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;01&lt;/TD&gt;&lt;TD&gt;010&lt;/TD&gt;&lt;TD&gt;01010&lt;/TD&gt;&lt;TD&gt;01|010&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;010&lt;/TD&gt;&lt;TD&gt;10&lt;/TD&gt;&lt;TD&gt;01010&lt;/TD&gt;&lt;TD&gt;010|10&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this admittedly trivial example a straight concatenation of FieldA and FieldB results in keys which clash. Inserting a delimiter character between them eliminates this possibility&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2019 12:22:28 GMT</pubDate>
    <dc:creator>marcus_malinow</dc:creator>
    <dc:date>2019-08-01T12:22:28Z</dc:date>
    <item>
      <title>Concatenating two fields, giving rise to App performance issue or slow</title>
      <link>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608367#M597353</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am concatenating two fields, ‘Field_A’ &amp;amp; ‘Field_B’ as ‘Field_C’ in script.&lt;/P&gt;&lt;P&gt;The file size increased when I do this, as both fields have 45 million records/rows each.&lt;/P&gt;&lt;P&gt;The App performance also decreased, app became slow.&lt;/P&gt;&lt;P&gt;App size is 1 GB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please help me, in any alternative to this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in Advance!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Heena Kauser&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 02:50:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608367#M597353</guid>
      <dc:creator>Heena</dc:creator>
      <dc:date>2024-11-16T02:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: Concatenating two fields, giving rise to App performance issue or slow</title>
      <link>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608379#M597354</link>
      <description>&lt;P&gt;Hi Heena,&amp;nbsp;&lt;/P&gt;&lt;P&gt;If your fields are large, or have high cardinality this is expected.&lt;/P&gt;&lt;P&gt;What is your reason for doing this? If for example it's because you are creating a composite key you could try using Autonumber.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Marcus&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 08:31:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608379#M597354</guid>
      <dc:creator>marcus_malinow</dc:creator>
      <dc:date>2019-08-01T08:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: Concatenating two fields, giving rise to App performance issue or slow</title>
      <link>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608448#M597356</link>
      <description>&lt;P&gt;Hi Marcus,&lt;/P&gt;&lt;P&gt;The Reason: to get unique key out of those two fields.&lt;/P&gt;&lt;P&gt;Thanks for your suggestion, working on it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Heena Kauser&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 11:05:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608448#M597356</guid>
      <dc:creator>Heena</dc:creator>
      <dc:date>2019-08-01T11:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: Concatenating two fields, giving rise to App performance issue or slow</title>
      <link>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608496#M597357</link>
      <description>&lt;P&gt;Thought that might be the reason, in which case I'd suggest including a delimiter between your two fields in order to avoid possible linking issues.&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;FieldA&lt;/TD&gt;&lt;TD&gt;FieldB&lt;/TD&gt;&lt;TD&gt;FieldA &amp;amp; FieldB as FieldC&lt;/TD&gt;&lt;TD&gt;FieldA &amp;amp; '|' &amp;amp; FieldB as FieldC&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;01&lt;/TD&gt;&lt;TD&gt;010&lt;/TD&gt;&lt;TD&gt;01010&lt;/TD&gt;&lt;TD&gt;01|010&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;010&lt;/TD&gt;&lt;TD&gt;10&lt;/TD&gt;&lt;TD&gt;01010&lt;/TD&gt;&lt;TD&gt;010|10&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this admittedly trivial example a straight concatenation of FieldA and FieldB results in keys which clash. Inserting a delimiter character between them eliminates this possibility&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 12:22:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Concatenating-two-fields-giving-rise-to-App-performance-issue-or/m-p/1608496#M597357</guid>
      <dc:creator>marcus_malinow</dc:creator>
      <dc:date>2019-08-01T12:22:28Z</dc:date>
    </item>
  </channel>
</rss>

