<?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: Creating fields based on each other - best approach in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235104#M393007</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Preceding load is better than Resident I guess&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Dec 2016 07:59:11 GMT</pubDate>
    <dc:creator>shraddha_g</dc:creator>
    <dc:date>2016-12-09T07:59:11Z</dc:date>
    <item>
      <title>Creating fields based on each other - best approach</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235101#M393004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a rather large QVD file containing ~7 Million records.&lt;/P&gt;&lt;P&gt;These deal with usage data And I have a Teradata script that I need to rebuild with Qlikview logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Teradata it was like&lt;/P&gt;&lt;P&gt;SELECT&lt;/P&gt;&lt;P&gt; field1,&lt;/P&gt;&lt;P&gt; field2,&lt;/P&gt;&lt;P&gt; field1+field2 newField1&lt;/P&gt;&lt;P&gt; newField1/field1 newField2&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a simplified example, there are complex calculations in the original script.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as I know, I can only create newField1 in the same step:&lt;/P&gt;&lt;P&gt;LOAD *,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; field1+field2 as newField1&lt;/P&gt;&lt;P&gt;FROM ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What about newField2? Do I Need to insert the complex calculations instead using the Name:&lt;/P&gt;&lt;P&gt;LOAD *,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; field1+field2 as newField1,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (field1+field2)/field1 as newField2&lt;/P&gt;&lt;P&gt;FROM ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will drive me mad....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or do another load over all records to add the field? This will take a lot of time...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any advice &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2016 05:56:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235101#M393004</guid>
      <dc:creator />
      <dc:date>2016-12-09T05:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: Creating fields based on each other - best approach</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235102#M393005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try preceding load&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Load *,newField1/field1 as newField2;&lt;/P&gt;&lt;P&gt;LOAD *,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; field1+field2 as newField1&lt;/P&gt;&lt;P&gt;FROM ....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2016 06:00:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235102#M393005</guid>
      <dc:creator>shraddha_g</dc:creator>
      <dc:date>2016-12-09T06:00:57Z</dc:date>
    </item>
    <item>
      <title>Re: Creating fields based on each other - best approach</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235103#M393006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alright, thanks.&lt;/P&gt;&lt;P&gt;Is this the fastest option, by the way? I needed 6 preceding loads overall because of all the dependencies and the load now takes about 17 minutes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2016 07:43:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235103#M393006</guid>
      <dc:creator />
      <dc:date>2016-12-09T07:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: Creating fields based on each other - best approach</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235104#M393007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Preceding load is better than Resident I guess&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2016 07:59:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235104#M393007</guid>
      <dc:creator>shraddha_g</dc:creator>
      <dc:date>2016-12-09T07:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: Creating fields based on each other - best approach</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235105#M393008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm still not satisfied with the load time. Anyhow, you're answer is correct, marked it accordingly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2016 08:38:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-fields-based-on-each-other-best-approach/m-p/1235105#M393008</guid>
      <dc:creator />
      <dc:date>2016-12-09T08:38:18Z</dc:date>
    </item>
  </channel>
</rss>

