<?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: Derived Fields not working in Qlik Sense Feb 2024 IR in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2451223#M97995</link>
    <description>&lt;P&gt;This is still happen in our production environment which has now been upgraded to February 2024 Patch 2&lt;/P&gt;
&lt;P&gt;Anyone else experiencing this or have a fix ?&lt;/P&gt;</description>
    <pubDate>Fri, 10 May 2024 16:00:34 GMT</pubDate>
    <dc:creator>lobmeister165</dc:creator>
    <dc:date>2024-05-10T16:00:34Z</dc:date>
    <item>
      <title>Derived Fields not working in Qlik Sense Feb 2024 IR</title>
      <link>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2420774#M95659</link>
      <description>&lt;P&gt;I have just installed Feb 2024 on a lab server for testing.&lt;/P&gt;
&lt;P&gt;Have imported one of our production apps (from Feb 2022 cluster) which uses derived fields for calendar dimensions using the &lt;STRONG&gt;DECLARE FIELD DEFINITION....FIELDS and DERIVE FIELDS FROM FIELDS .... USING ....&lt;/STRONG&gt; script construction&lt;/P&gt;
&lt;P&gt;There seems to be a &lt;STRONG&gt;bug&lt;/STRONG&gt; with the derived fields&amp;nbsp; - it recognises them and shows them in field list but in expression editor it reports an &lt;STRONG&gt;error in expression with red border round field box&lt;/STRONG&gt; and when using the derived fields in conjunction with a function - in this case the CLASS function it does not work and returns an error&lt;/P&gt;
&lt;P&gt;This all works 100% OK in our Feb 2022 production environment&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone else encountered this ?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Feb 2024 14:17:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2420774#M95659</guid>
      <dc:creator>lobmeister165</dc:creator>
      <dc:date>2024-02-19T14:17:11Z</dc:date>
    </item>
    <item>
      <title>Re: Derived Fields not working in Qlik Sense Feb 2024 IR</title>
      <link>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2451223#M97995</link>
      <description>&lt;P&gt;This is still happen in our production environment which has now been upgraded to February 2024 Patch 2&lt;/P&gt;
&lt;P&gt;Anyone else experiencing this or have a fix ?&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 16:00:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2451223#M97995</guid>
      <dc:creator>lobmeister165</dc:creator>
      <dc:date>2024-05-10T16:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: Derived Fields not working in Qlik Sense Feb 2024 IR</title>
      <link>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2452462#M98086</link>
      <description>&lt;P&gt;Have now discovered this was due to variables being used in our bespoke script for driving date fields in multiple calendars, without wrapping in dollar syntax. This did work on Feb 2022, but it would appear that Feb 2024 is stricter when parsing the script and requires the dollar sign syntax if including variable references&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2024 23:11:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Derived-Fields-not-working-in-Qlik-Sense-Feb-2024-IR/m-p/2452462#M98086</guid>
      <dc:creator>lobmeister165</dc:creator>
      <dc:date>2024-05-14T23:11:36Z</dc:date>
    </item>
  </channel>
</rss>

