<?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 Aliasing Fields using Data Definitions in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342015#M706234</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Josh.&lt;/P&gt;&lt;P&gt;This is very good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, in some cases the datasource field names are coded, i.e TLBKID, TRTTYP.&lt;/P&gt;&lt;P&gt;As a developer I would normally rename the fields on which I do something (where clauses, if statements etc.) in the beginning of the script, for better readability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then at the end of the script I could use your technique to rename the rest of the fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/21613"&gt;Magnus Åvitsland&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BI Consultant&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.framsteg.com" target="_blank"&gt;Framsteg Business Intelligence Corp.&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Mar 2012 09:22:10 GMT</pubDate>
    <dc:creator>magavi_framsteg</dc:creator>
    <dc:date>2012-03-08T09:22:10Z</dc:date>
    <item>
      <title>Aliasing Fields using Data Definitions</title>
      <link>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342014#M706233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This videos show how to use a data dictionaryto alias (or rename) fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://youtu.be/Cyjg4LQN9Vo"&gt;http://youtu.be/Cyjg4LQN9Vo&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;IFRAME frameborder="0" width="425" height="350" src="https://www.youtube.com/embed/Cyjg4LQN9Vo" allowfullscreen=""&gt;&lt;/IFRAME&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2012 01:19:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342014#M706233</guid>
      <dc:creator>Josh_Good</dc:creator>
      <dc:date>2012-03-08T01:19:10Z</dc:date>
    </item>
    <item>
      <title>Aliasing Fields using Data Definitions</title>
      <link>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342015#M706234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Josh.&lt;/P&gt;&lt;P&gt;This is very good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, in some cases the datasource field names are coded, i.e TLBKID, TRTTYP.&lt;/P&gt;&lt;P&gt;As a developer I would normally rename the fields on which I do something (where clauses, if statements etc.) in the beginning of the script, for better readability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then at the end of the script I could use your technique to rename the rest of the fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/21613"&gt;Magnus Åvitsland&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BI Consultant&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.framsteg.com" target="_blank"&gt;Framsteg Business Intelligence Corp.&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2012 09:22:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342015#M706234</guid>
      <dc:creator>magavi_framsteg</dc:creator>
      <dc:date>2012-03-08T09:22:10Z</dc:date>
    </item>
    <item>
      <title>Aliasing Fields using Data Definitions</title>
      <link>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342016#M706235</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Very good point Magnus.&amp;nbsp; This technique can be used in combination with manual aliasing.&amp;nbsp; QlikView will simply keep the manually aliased names and replace the ones that have not been manually aliased.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards,&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2012 16:02:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/342016#M706235</guid>
      <dc:creator>Josh_Good</dc:creator>
      <dc:date>2012-03-08T16:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: Aliasing Fields using Data Definitions</title>
      <link>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/1752015#M706236</link>
      <description>&lt;P&gt;This was helpful. Thank You&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2020 13:34:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Aliasing-Fields-using-Data-Definitions/m-p/1752015#M706236</guid>
      <dc:creator>pam1990</dc:creator>
      <dc:date>2020-10-13T13:34:56Z</dc:date>
    </item>
  </channel>
</rss>

