<?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 Cascading or Nested Alternate States in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Cascading-or-Nested-Alternate-States/m-p/1729610#M455487</link>
    <description>&lt;P&gt;I have a requirement to show engagement for a series of emails, and we want to see how recipients react with successive emails through the journey.&amp;nbsp; I have this set up and working using set analysis in variables and dynamic expressions, but I'm wondering if there is a better, more efficient way of achieving this (and maintaining it).&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have attached a sample document for reference.&amp;nbsp; Basically what should happen is that the user makes a selection in AltState1 then each subsequent State takes the profiles included in the previous state and overlays it's own filters, the 3rd state takes profiles that are included in States 1 and 2, etc. As of now, I'm using intersections in set analysis to accomplish this:&lt;/P&gt;&lt;P&gt;Set1: {&amp;lt;EmailSent_count = {'&amp;gt;0'}&amp;gt;}&lt;/P&gt;&lt;P&gt;Set2:&amp;nbsp;{&amp;lt;EmailSent_count = {'&amp;gt;0'}&amp;gt;*&amp;lt;em_ProfileID = p({Set1&amp;lt;EmailSent_count = {'&amp;gt;0'}&amp;gt;} em_ProfileID)&amp;gt;} ... and so on&lt;/P&gt;&lt;P&gt;I'm setting this all up in variables so I can piece the bits of set analysis code together as needed for each chart, making it as modular as I know now, but i wonder if there is a better way.&amp;nbsp; Also would be nice if this rule considering previous States would affect the possible values showing in each state's filters.&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 00:17:20 GMT</pubDate>
    <dc:creator>ANCasselman</dc:creator>
    <dc:date>2024-11-16T00:17:20Z</dc:date>
    <item>
      <title>Cascading or Nested Alternate States</title>
      <link>https://community.qlik.com/t5/QlikView/Cascading-or-Nested-Alternate-States/m-p/1729610#M455487</link>
      <description>&lt;P&gt;I have a requirement to show engagement for a series of emails, and we want to see how recipients react with successive emails through the journey.&amp;nbsp; I have this set up and working using set analysis in variables and dynamic expressions, but I'm wondering if there is a better, more efficient way of achieving this (and maintaining it).&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have attached a sample document for reference.&amp;nbsp; Basically what should happen is that the user makes a selection in AltState1 then each subsequent State takes the profiles included in the previous state and overlays it's own filters, the 3rd state takes profiles that are included in States 1 and 2, etc. As of now, I'm using intersections in set analysis to accomplish this:&lt;/P&gt;&lt;P&gt;Set1: {&amp;lt;EmailSent_count = {'&amp;gt;0'}&amp;gt;}&lt;/P&gt;&lt;P&gt;Set2:&amp;nbsp;{&amp;lt;EmailSent_count = {'&amp;gt;0'}&amp;gt;*&amp;lt;em_ProfileID = p({Set1&amp;lt;EmailSent_count = {'&amp;gt;0'}&amp;gt;} em_ProfileID)&amp;gt;} ... and so on&lt;/P&gt;&lt;P&gt;I'm setting this all up in variables so I can piece the bits of set analysis code together as needed for each chart, making it as modular as I know now, but i wonder if there is a better way.&amp;nbsp; Also would be nice if this rule considering previous States would affect the possible values showing in each state's filters.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 00:17:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cascading-or-Nested-Alternate-States/m-p/1729610#M455487</guid>
      <dc:creator>ANCasselman</dc:creator>
      <dc:date>2024-11-16T00:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cascading or Nested Alternate States</title>
      <link>https://community.qlik.com/t5/QlikView/Cascading-or-Nested-Alternate-States/m-p/1733275#M455488</link>
      <description>&lt;P&gt;Best I can offer are the following:&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/LoadData/best-practices-data-modeling.htm" target="_blank"&gt;https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/LoadData/best-practices-data-modeling.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/application-performance-optimization.htm" target="_blank"&gt;https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/application-performance-optimization.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Hopefully they may be of some help to confirm if you have done best practices with things.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2020 20:27:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cascading-or-Nested-Alternate-States/m-p/1733275#M455488</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2020-08-04T20:27:00Z</dc:date>
    </item>
  </channel>
</rss>

