<?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: simplifying to reduce repetitive set conditions in expressions in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/simplifying-to-reduce-repetitive-set-conditions-in-expressions/m-p/2008214#M1221622</link>
    <description>&lt;P&gt;There are probably not many possibilities to optimize this expression directly.&lt;/P&gt;
&lt;P&gt;More effects would have to reduce the number of concurrent visible objects respectively to merge multiple objects. The last means not to use n separate KPI objects else using a table-chart for them. This reduced layout-options but it would also reduce the efforts to develop and maintain the UI.&lt;/P&gt;
&lt;P&gt;Further some of the expression-conditions might be transferrable to the dimensional layer - with and/or without adjustments to the data-model. The data-model itself is very important for the UI performance - officially recommended as best compromise in regard to efforts, readability, maintainability and performance is a star-scheme data-model.&lt;/P&gt;
&lt;P&gt;- Marcus&lt;/P&gt;</description>
    <pubDate>Wed, 23 Nov 2022 13:02:43 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2022-11-23T13:02:43Z</dc:date>
    <item>
      <title>simplifying to reduce repetitive set conditions in expressions</title>
      <link>https://community.qlik.com/t5/QlikView/simplifying-to-reduce-repetitive-set-conditions-in-expressions/m-p/2007634#M1221599</link>
      <description>&lt;DIV class="ewa-rteLine"&gt;Hi Folks,&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;I am looking for simplification of chart/kpi expressions from last few days for an existing qliksense app. The app has quite a large no. of objects with such expressions which is slowing it down.&amp;nbsp; I'm not able to figure out a simple way to do this. Looking for any help and suggestions.&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;pls find one sample expression below:&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;This is for calculating change in distance travelled since last week.&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;Num((((Sum({&amp;lt; [delivery_completion_date]=P({&amp;lt;[delivery_completion_date]={"&amp;gt;=$(=date(vCurr_wk_start,'YYYY/MM/DD'))&amp;lt;=$(=date(vCurr_wk_end,'YYYY/MM/DD'))"},Date=,WeekYear_Num=,WeekYear=,MonthYear=&amp;gt;}),MonthYear=,Date= ,WeekYear=,WeekYear_Num=,[safety_ex]={'N'} , [max_dist_km]={"&amp;gt;0"} , Category={"g"}, max_dispatch_dist={'Y'} &amp;gt;} [max_dist_km] )&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;/&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;Sum({&amp;lt; [delivery_completion_date]=P({&amp;lt;[delivery_completion_date]={"&amp;gt;=$(=date(vCurr_wk_start,'YYYY/MM/DD'))&amp;lt;=$(=date(vCurr_wk_end,'YYYY/MM/DD'))"},Date=,WeekYear_Num=,WeekYear=,MonthYear=&amp;gt;}),MonthYear=,Date=, WeekYear_Num=,WeekYear=,[safety_ex]={'N'} , [max_dist_km]={"&amp;gt;0"} , Category={"g","r","y"}, max_dispatch_dist={'Y'} &amp;gt;} [max_dist_km]) )&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;-&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;(Sum({&amp;lt; [delivery_completion_date]=P({&amp;lt;[delivery_completion_date]={"&amp;gt;=$(=date(vlast_wk_start,'YYYY/MM/DD'))&amp;lt;=$(=date(vlast_wk_end,'YYYY/MM/DD'))"},Date=,WeekYear_Num=,WeekYear=,MonthYear=&amp;gt;}),MonthYear=,Date= ,WeekYear=,WeekYear_Num=,[safety_ex]={'N'} , [max_dist_km]={"&amp;gt;0"} , Category={"g"}, max_dispatch_dist={'Y'} &amp;gt;} [max_dist_km] )&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;/&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;Sum({&amp;lt; [delivery_completion_date]=P({&amp;lt;[delivery_completion_date]={"&amp;gt;=$(=date(vlast_wk_start,'YYYY/MM/DD'))&amp;lt;=$(=date(vlast_wk_end,'YYYY/MM/DD'))"},Date=,WeekYear_Num=,WeekYear=,MonthYear=&amp;gt;}),MonthYear=,Date=, WeekYear_Num=,WeekYear=,[safety_ex]={'N'} , [max_dist_km]={"&amp;gt;0"} , Category={"g","r","y"}, max_dispatch_dist={'Y'} &amp;gt;} [max_dist_km]) )&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;)),'0.0%')&lt;/DIV&gt;
&lt;DIV class="ewa-rteLine"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 22 Nov 2022 14:15:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/simplifying-to-reduce-repetitive-set-conditions-in-expressions/m-p/2007634#M1221599</guid>
      <dc:creator>anu</dc:creator>
      <dc:date>2022-11-22T14:15:45Z</dc:date>
    </item>
    <item>
      <title>Re: simplifying to reduce repetitive set conditions in expressions</title>
      <link>https://community.qlik.com/t5/QlikView/simplifying-to-reduce-repetitive-set-conditions-in-expressions/m-p/2008214#M1221622</link>
      <description>&lt;P&gt;There are probably not many possibilities to optimize this expression directly.&lt;/P&gt;
&lt;P&gt;More effects would have to reduce the number of concurrent visible objects respectively to merge multiple objects. The last means not to use n separate KPI objects else using a table-chart for them. This reduced layout-options but it would also reduce the efforts to develop and maintain the UI.&lt;/P&gt;
&lt;P&gt;Further some of the expression-conditions might be transferrable to the dimensional layer - with and/or without adjustments to the data-model. The data-model itself is very important for the UI performance - officially recommended as best compromise in regard to efforts, readability, maintainability and performance is a star-scheme data-model.&lt;/P&gt;
&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 13:02:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/simplifying-to-reduce-repetitive-set-conditions-in-expressions/m-p/2008214#M1221622</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2022-11-23T13:02:43Z</dc:date>
    </item>
  </channel>
</rss>

