<?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: island table - impacting data model in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/island-table-impacting-data-model/m-p/2426612#M13448</link>
    <description>&lt;P&gt;The used approach seems to be more complicated as necessary. Just to ignore some selections it's not necessary to use alternate states because these selections could be ignored within a set analysis.&lt;/P&gt;
&lt;P&gt;If I understand the applied data-model with the island tables right - just in duplicating two fields within separate tables - and querying later those selections within set analysis it should work very well and could be done quite simply without any variables and/or buttons and selections, for example with something like:&lt;/P&gt;
&lt;P&gt;count({&amp;lt; Filter2, Filter1 = p(IslandFilter1) &amp;gt;} Field)&lt;/P&gt;
&lt;P&gt;and similar by the other charts. To show further which selections of the filter-fields are applied you could just query the island-table, like:&lt;/P&gt;
&lt;P&gt;concat(IslandFilter1, ' + ')&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 04 Mar 2024 12:29:57 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2024-03-04T12:29:57Z</dc:date>
    <item>
      <title>island table - impacting data model</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/island-table-impacting-data-model/m-p/2426298#M13442</link>
      <description>&lt;P&gt;Problem Statement :&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mansi_Gupta1_1-1709488375463.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/161171iF4743C3CB98884B5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Mansi_Gupta1_1-1709488375463.png" alt="Mansi_Gupta1_1-1709488375463.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;In UI we have 3 charts&lt;BR /&gt;chart1 should not be impacted by chart 2 and chart3&lt;BR /&gt;so we initially gave alternate state to chart2 and chart3.(these charts are working with global filters-which are shown in top through scope operator)&lt;/P&gt;
&lt;P&gt;However this was impacting UI performance badly. So we are trying to achieve this through data model.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Data Model Table:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;KeyField (having values a b c d..)&lt;/STRONG&gt;&lt;BR /&gt;field1&lt;BR /&gt;field2&lt;BR /&gt;field3&lt;BR /&gt;field4&lt;BR /&gt;.&lt;BR /&gt;.Chart 1 uses keyfield and field 3, field 4 here. (field 1 and field 2 are for remaining charts)&lt;BR /&gt;&lt;BR /&gt;Island table 1 : (residented data model table)&lt;BR /&gt;&lt;STRONG&gt;KeyField as KeyField1 (having values a b c d..)&lt;BR /&gt;&lt;/STRONG&gt;field1 as field11&lt;BR /&gt;&lt;BR /&gt;Island table 2 :&amp;nbsp;(residented data model table)&lt;BR /&gt;&lt;STRONG&gt;KeyField as KeyField2 (having values a b c d..)&lt;BR /&gt;&lt;/STRONG&gt;field2 as field22&lt;BR /&gt;&lt;BR /&gt;in UI :&lt;BR /&gt;in filter2 we are giving field11 when keyfield1 matches &lt;STRONG&gt;a &lt;/STRONG&gt;value (amongst the list)&lt;BR /&gt;in chart 2 we are giving expression :&lt;/P&gt;
&lt;P&gt;count({&amp;lt;keyfield={variable(definition : trigger in page selects &lt;STRONG&gt;a&lt;/STRONG&gt;)}&amp;gt;}field11)&lt;BR /&gt;&lt;BR /&gt;what is happening ..&lt;BR /&gt;in selection area it shows variable &lt;STRONG&gt;a&lt;/STRONG&gt; selected..&lt;BR /&gt;&lt;BR /&gt;when we are navigating to next page where variable value&amp;nbsp;&lt;STRONG&gt;b&lt;/STRONG&gt; should be selected.. it does not overwrite that.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 03 Mar 2024 18:03:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/island-table-impacting-data-model/m-p/2426298#M13442</guid>
      <dc:creator>Mansi_Gupta1</dc:creator>
      <dc:date>2024-03-03T18:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: island table - impacting data model</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/island-table-impacting-data-model/m-p/2426612#M13448</link>
      <description>&lt;P&gt;The used approach seems to be more complicated as necessary. Just to ignore some selections it's not necessary to use alternate states because these selections could be ignored within a set analysis.&lt;/P&gt;
&lt;P&gt;If I understand the applied data-model with the island tables right - just in duplicating two fields within separate tables - and querying later those selections within set analysis it should work very well and could be done quite simply without any variables and/or buttons and selections, for example with something like:&lt;/P&gt;
&lt;P&gt;count({&amp;lt; Filter2, Filter1 = p(IslandFilter1) &amp;gt;} Field)&lt;/P&gt;
&lt;P&gt;and similar by the other charts. To show further which selections of the filter-fields are applied you could just query the island-table, like:&lt;/P&gt;
&lt;P&gt;concat(IslandFilter1, ' + ')&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2024 12:29:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/island-table-impacting-data-model/m-p/2426612#M13448</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2024-03-04T12:29:57Z</dc:date>
    </item>
  </channel>
</rss>

