<?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: Select Exluded Trigger for an If-else condition in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Select-Exluded-Trigger-for-an-If-else-condition/m-p/1970210#M80047</link>
    <description>&lt;P&gt;An exclusion could for example be reached with a heading minus-sign. Just play with it directly on a list-box. If you could set the wanted selections and comprehends the logic you may adapt it to the macro- and/or action-stuff.&lt;/P&gt;
&lt;P&gt;But I suggest to avoid such approaches in general because of the needed complexity and efforts to create and maintain such logic and the worse usability which comes often with it. Within a normal data-model such stuff won't be needed because everything is appropriate related to each other and could be directly selected and for advanced views a set analysis could be applied to ignore/overwrite selections - especially the p() and e() functions are very powerful.&lt;/P&gt;
&lt;P&gt;Just for reference see:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Macros-are-Bad/ba-p/1466215" target="_blank"&gt;Macros are Bad - Qlik Community - 1466215&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Let-the-User-Select/ba-p/1463978" target="_blank"&gt;Let the User Select - Qlik Community - 1463978&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;- Marcus&lt;/P&gt;</description>
    <pubDate>Thu, 18 Aug 2022 10:52:03 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2022-08-18T10:52:03Z</dc:date>
    <item>
      <title>Select Exluded Trigger for an If-else condition</title>
      <link>https://community.qlik.com/t5/App-Development/Select-Exluded-Trigger-for-an-If-else-condition/m-p/1970032#M80032</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am in the process of eliminating selections made with the help of macros and convert them into field event trigger based selections.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One scenario in this is proving to be very difficult to convert. As you can see the macro script contains an If-else condition where in the first condition, the select excluded functionality is being used.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="572_varuag_0-1660799296417.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/86960i62136B5C78A96BCA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="572_varuag_0-1660799296417.png" alt="572_varuag_0-1660799296417.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I was able to replicate the If-else condition but how do I get QV Triggers to exclude the values selected in the last line of my if condition.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="572_varuag_1-1660799425777.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/86961i33BBC70E8068A171/image-size/medium?v=v2&amp;amp;px=400" role="button" title="572_varuag_1-1660799425777.png" alt="572_varuag_1-1660799425777.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Aug 2022 05:12:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Select-Exluded-Trigger-for-an-If-else-condition/m-p/1970032#M80032</guid>
      <dc:creator>572_varuag</dc:creator>
      <dc:date>2022-08-18T05:12:36Z</dc:date>
    </item>
    <item>
      <title>Re: Select Exluded Trigger for an If-else condition</title>
      <link>https://community.qlik.com/t5/App-Development/Select-Exluded-Trigger-for-an-If-else-condition/m-p/1970210#M80047</link>
      <description>&lt;P&gt;An exclusion could for example be reached with a heading minus-sign. Just play with it directly on a list-box. If you could set the wanted selections and comprehends the logic you may adapt it to the macro- and/or action-stuff.&lt;/P&gt;
&lt;P&gt;But I suggest to avoid such approaches in general because of the needed complexity and efforts to create and maintain such logic and the worse usability which comes often with it. Within a normal data-model such stuff won't be needed because everything is appropriate related to each other and could be directly selected and for advanced views a set analysis could be applied to ignore/overwrite selections - especially the p() and e() functions are very powerful.&lt;/P&gt;
&lt;P&gt;Just for reference see:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Macros-are-Bad/ba-p/1466215" target="_blank"&gt;Macros are Bad - Qlik Community - 1466215&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Let-the-User-Select/ba-p/1463978" target="_blank"&gt;Let the User Select - Qlik Community - 1463978&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Thu, 18 Aug 2022 10:52:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Select-Exluded-Trigger-for-an-If-else-condition/m-p/1970210#M80047</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2022-08-18T10:52:03Z</dc:date>
    </item>
  </channel>
</rss>

