<?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: [best practice] how to decode numeric values into intelligible strings in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417859#M697685</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for the awful delay in asnwering and indeed thank you for the replies of you all, much appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hinestly, I still do not understand what would be the difference between a "simple" solution like &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_text_macro jive_macro_code _jivemacro_uid_13661996140082753" jivemacro_uid="_13661996140082753"&gt;&lt;P&gt;names:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD * INLINE [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SCONL, Names&lt;/P&gt;&lt;P&gt;AA, Warehouse 1&lt;/P&gt;&lt;P&gt;AB, Warehouse 2&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and going through the ApplyMap function, linked to an inline table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it just a matter of "script developing etiquette"? Or are there real advantages connected to it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks again for your support!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Apr 2013 11:58:06 GMT</pubDate>
    <dc:creator />
    <dc:date>2013-04-17T11:58:06Z</dc:date>
    <item>
      <title>[best practice] how to decode numeric values into intelligible strings</title>
      <link>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417855#M697681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a table in AS400 which is carrying a hefty number of fields populated by numeric values (usually no more than 4).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Those numeric values have of course a meaning behidn it, and here I am asking to you what is the best practice to accomplish that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I can think of is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A. LOAD INLINE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;creating &lt;EM&gt;x&lt;/EM&gt; INLINE tables as the &lt;EM&gt;x&lt;/EM&gt; fields that need this translation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;B. IF in the script&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in the LOAD script of this AS400 table, writing the script as (if(field=1,'apple', if(field=2, 'banana', 'mango'))&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C. IF in the QVW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simply, in the UI lsit box or table, I input there the IF statement to "translate" the numeric values&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best approach? and further, are there some other approaches?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for your opinions!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2013 11:44:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417855#M697681</guid>
      <dc:creator />
      <dc:date>2013-03-07T11:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: [best practice] how to decode numeric values into intelligible strings</title>
      <link>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417856#M697682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can tell you the worst practice is using IF in expressions or dimensions, I should use the B) solution (but even the A) is good .... take even a look to the keyword MAP that is very useful in those cases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopeit helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2013 12:12:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417856#M697682</guid>
      <dc:creator>alexandros17</dc:creator>
      <dc:date>2013-03-07T12:12:03Z</dc:date>
    </item>
    <item>
      <title>Re: [best practice] how to decode numeric values into intelligible strings</title>
      <link>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417857#M697683</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;The best practice for this scenario is to create mapping tables (containing two fields, the code and the description). This can be done 3 ways:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;From your system database (if the mappings exist in the database). This has the advantage of no additional maintenance, but depends on the system.&lt;/LI&gt;&lt;LI&gt;From an external source, such as Excel files. These mappings could be maintained by a data administrator.&lt;/LI&gt;&lt;LI&gt;From inline tables. Simplest, but maintenance implies fiddling with the load script and could break the document.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use Mapping Load.... statements into named mapping tables, one for each mapping, eg:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MapItemType:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Mapping Load ItemTypeID, ItemTypeName &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; From ItemTypes;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then use ApplyMap during your load to bring the descriptions in:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Items:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LOAD ItemID,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ApplyMap('MapItemType', ItemTypeID) As ItemType,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ItemTypeID,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; From Items;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You probably dont actually need the ItemTypeID after you have loaded, in which case you can omit the ItemTypeID line. Now the table contains the ItemType Descriptions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;Jonathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2013 13:04:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417857#M697683</guid>
      <dc:creator>jonathandienst</dc:creator>
      <dc:date>2013-03-07T13:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: [best practice] how to decode numeric values into intelligible strings</title>
      <link>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417858#M697684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would do it exactly like &lt;A _jive_internal="true" class="jiveTT-hover-user jive-username-link" href="https://community.qlik.com/people/jontydkpi" id="jive-1322916110999751417229" style="background-color: #ffffff; font-size: 12px; color: #007fc0; font-weight: bold; font-family: Arial; text-align: center;"&gt;Jonathan Dienst&lt;/A&gt; describes it. See more on &lt;A _jive_internal="true" class="loading" href="https://community.qlik.com/blogs/qlikviewdesignblog/2012/09/18/one-favorite-function-applymap" title="http://community.qlik.com/blogs/qlikviewdesignblog/2012/09/18/one-favorite-function-applymap"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2012/09/18/one-favorite-function-applymap&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Mar 2013 08:29:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417858#M697684</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2013-03-08T08:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: [best practice] how to decode numeric values into intelligible strings</title>
      <link>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417859#M697685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for the awful delay in asnwering and indeed thank you for the replies of you all, much appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hinestly, I still do not understand what would be the difference between a "simple" solution like &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_text_macro jive_macro_code _jivemacro_uid_13661996140082753" jivemacro_uid="_13661996140082753"&gt;&lt;P&gt;names:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD * INLINE [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SCONL, Names&lt;/P&gt;&lt;P&gt;AA, Warehouse 1&lt;/P&gt;&lt;P&gt;AB, Warehouse 2&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and going through the ApplyMap function, linked to an inline table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it just a matter of "script developing etiquette"? Or are there real advantages connected to it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks again for your support!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Apr 2013 11:58:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/best-practice-how-to-decode-numeric-values-into-intelligible/m-p/417859#M697685</guid>
      <dc:creator />
      <dc:date>2013-04-17T11:58:06Z</dc:date>
    </item>
  </channel>
</rss>

