<?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: Want to clear the selection for the table From the sheet which is not using that field in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2497813#M102783</link>
    <description>&lt;H4&gt;&lt;STRONG&gt;Direct Answer to the Question:&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;There isn’t a built-in way in Qlik Sense to dynamically clear selections for &lt;STRONG&gt;multiple fields (wildcard)&lt;/STRONG&gt; from one table when navigating between sheets. Instead, any field-specific clearing requires manually creating actions for each field, which can be cumbersome if there are many fields. However, there are two practical approaches to address this:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Using Bookmarks&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Create a bookmark with no selections applied.&lt;/LI&gt;
&lt;LI&gt;Add a single action to each sheet that applies this bookmark when the user navigates to that sheet. This ensures irrelevant selections (e.g., &lt;CODE&gt;H_OrderNo&lt;/CODE&gt;) are cleared automatically.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Splitting the App&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If the workflows for Historical and Current Orders are largely independent, consider splitting the app into two separate apps:
&lt;UL&gt;
&lt;LI&gt;One for Historical Orders.&lt;/LI&gt;
&lt;LI&gt;Another for Current Orders.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;This ensures selections remain relevant and reduces confusion while keeping the data models more focused.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;HR /&gt;
&lt;H4&gt;&lt;STRONG&gt;Guidance for Improving the Data Model&lt;/STRONG&gt;:&lt;/H4&gt;
&lt;P&gt;Looking at the app structure in your diagram, I’d recommend consolidating the &lt;CODE&gt;Current Order Table&lt;/CODE&gt; and &lt;CODE&gt;Historical Order Table&lt;/CODE&gt; into a single table. This simplifies the app and avoids many of these issues. Here’s how you can do it:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Add a "Type" Field&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Introduce a new field (e.g., &lt;CODE&gt;OrderType&lt;/CODE&gt;) that identifies whether each row belongs to "Current" or "Historical" orders.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Concatenate the Tables&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Combine the fields (&lt;CODE&gt;OrderNo&lt;/CODE&gt;, &lt;CODE&gt;Location&lt;/CODE&gt;, and &lt;CODE&gt;Status&lt;/CODE&gt;) from both tables into one unified table, using the &lt;CODE&gt;OrderType&lt;/CODE&gt; field to differentiate between the two datasets. The result would look like this:&lt;/LI&gt;
&lt;/UL&gt;
&lt;TABLE&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH&gt;OrderNo&lt;/TH&gt;
&lt;TH&gt;Location&lt;/TH&gt;
&lt;TH&gt;Status&lt;/TH&gt;
&lt;TH&gt;OrderType&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;1&lt;/TD&gt;
&lt;TD&gt;ABC&lt;/TD&gt;
&lt;TD&gt;Pending&lt;/TD&gt;
&lt;TD&gt;Current&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;2&lt;/TD&gt;
&lt;TD&gt;DEF&lt;/TD&gt;
&lt;TD&gt;Dispatched&lt;/TD&gt;
&lt;TD&gt;Current&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;11&lt;/TD&gt;
&lt;TD&gt;ABC&lt;/TD&gt;
&lt;TD&gt;Delivered&lt;/TD&gt;
&lt;TD&gt;Historical&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;12&lt;/TD&gt;
&lt;TD&gt;DEF&lt;/TD&gt;
&lt;TD&gt;Delivered&lt;/TD&gt;
&lt;TD&gt;Historical&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Use Actions to Apply Filters Dynamically&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;For Historical Order sheets, add an action that applies a filter for &lt;CODE&gt;OrderType = 'Historical'&lt;/CODE&gt; when navigating to those sheets.&lt;/LI&gt;
&lt;LI&gt;For Current Order sheets, add an action that applies a filter for &lt;CODE&gt;OrderType = 'Current'&lt;/CODE&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;HR /&gt;
&lt;H4&gt;&lt;STRONG&gt;Why This Approach Works Better:&lt;/STRONG&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Simplified Data Model&lt;/STRONG&gt;: Consolidating the tables removes the need for duplicated fields (&lt;CODE&gt;H_OrderNo&lt;/CODE&gt;, &lt;CODE&gt;OrderNo&lt;/CODE&gt;) and makes the app more maintainable.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Better Performance&lt;/STRONG&gt;: A single table is more efficient for Qlik Sense to process than two separate tables.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Improved User Experience&lt;/STRONG&gt;: Users won’t be confused by irrelevant filters carrying over between unrelated sheets, as the filters will now be applied dynamically based on the sheet context.&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;H4&gt;&lt;STRONG&gt;Recommendation:&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;While the direct approaches using bookmarks or splitting the app are feasible, consolidating the data model with a single table is the most robust and scalable solution. It aligns with best practices in Qlik Sense and reduces the overall complexity of the app.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Dec 2024 05:04:54 GMT</pubDate>
    <dc:creator>nhenckel</dc:creator>
    <dc:date>2024-12-13T05:04:54Z</dc:date>
    <item>
      <title>Want to clear the selection for the table From the sheet which is not using that field</title>
      <link>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2496494#M102666</link>
      <description>&lt;P&gt;Hi Everyone,&lt;BR /&gt;&lt;BR /&gt;So right now I have 6 sheets from 2 independent table used, 3 sheet are using only Current order table field and other 2 only using Hisotrical order table, like below diagram I have made.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Fenil_0-1733479412307.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/175325i16F9F39CA97C38F6/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Fenil_0-1733479412307.png" alt="Fenil_0-1733479412307.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;So from the historical order table sheet's if i select H_Orderno or any other field and I go to sheet of Current order table, I don't want to see above selection for H_Orderno, Because it can confuse the user.&lt;BR /&gt;&lt;BR /&gt;Now I know I can add actions in each sheet for the field I want to ignore, But these all sheets are summary tables and contains more than 40 fields per sheet, So I have to add 40 actions per sheet which equals per 6 sheets is 240 Actions which is time consuming and I think can impact the performance.&lt;BR /&gt;&lt;BR /&gt;So do we have any other solution to get away from this situation?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Fenil Jain.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Dec 2024 10:13:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2496494#M102666</guid>
      <dc:creator>Fenil</dc:creator>
      <dc:date>2024-12-06T10:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: Want to clear the selection for the table From the sheet which is not using that field</title>
      <link>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2497813#M102783</link>
      <description>&lt;H4&gt;&lt;STRONG&gt;Direct Answer to the Question:&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;There isn’t a built-in way in Qlik Sense to dynamically clear selections for &lt;STRONG&gt;multiple fields (wildcard)&lt;/STRONG&gt; from one table when navigating between sheets. Instead, any field-specific clearing requires manually creating actions for each field, which can be cumbersome if there are many fields. However, there are two practical approaches to address this:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Using Bookmarks&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Create a bookmark with no selections applied.&lt;/LI&gt;
&lt;LI&gt;Add a single action to each sheet that applies this bookmark when the user navigates to that sheet. This ensures irrelevant selections (e.g., &lt;CODE&gt;H_OrderNo&lt;/CODE&gt;) are cleared automatically.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Splitting the App&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If the workflows for Historical and Current Orders are largely independent, consider splitting the app into two separate apps:
&lt;UL&gt;
&lt;LI&gt;One for Historical Orders.&lt;/LI&gt;
&lt;LI&gt;Another for Current Orders.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;This ensures selections remain relevant and reduces confusion while keeping the data models more focused.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;HR /&gt;
&lt;H4&gt;&lt;STRONG&gt;Guidance for Improving the Data Model&lt;/STRONG&gt;:&lt;/H4&gt;
&lt;P&gt;Looking at the app structure in your diagram, I’d recommend consolidating the &lt;CODE&gt;Current Order Table&lt;/CODE&gt; and &lt;CODE&gt;Historical Order Table&lt;/CODE&gt; into a single table. This simplifies the app and avoids many of these issues. Here’s how you can do it:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Add a "Type" Field&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Introduce a new field (e.g., &lt;CODE&gt;OrderType&lt;/CODE&gt;) that identifies whether each row belongs to "Current" or "Historical" orders.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Concatenate the Tables&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Combine the fields (&lt;CODE&gt;OrderNo&lt;/CODE&gt;, &lt;CODE&gt;Location&lt;/CODE&gt;, and &lt;CODE&gt;Status&lt;/CODE&gt;) from both tables into one unified table, using the &lt;CODE&gt;OrderType&lt;/CODE&gt; field to differentiate between the two datasets. The result would look like this:&lt;/LI&gt;
&lt;/UL&gt;
&lt;TABLE&gt;
&lt;THEAD&gt;
&lt;TR&gt;
&lt;TH&gt;OrderNo&lt;/TH&gt;
&lt;TH&gt;Location&lt;/TH&gt;
&lt;TH&gt;Status&lt;/TH&gt;
&lt;TH&gt;OrderType&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;1&lt;/TD&gt;
&lt;TD&gt;ABC&lt;/TD&gt;
&lt;TD&gt;Pending&lt;/TD&gt;
&lt;TD&gt;Current&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;2&lt;/TD&gt;
&lt;TD&gt;DEF&lt;/TD&gt;
&lt;TD&gt;Dispatched&lt;/TD&gt;
&lt;TD&gt;Current&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;11&lt;/TD&gt;
&lt;TD&gt;ABC&lt;/TD&gt;
&lt;TD&gt;Delivered&lt;/TD&gt;
&lt;TD&gt;Historical&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;12&lt;/TD&gt;
&lt;TD&gt;DEF&lt;/TD&gt;
&lt;TD&gt;Delivered&lt;/TD&gt;
&lt;TD&gt;Historical&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Use Actions to Apply Filters Dynamically&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;For Historical Order sheets, add an action that applies a filter for &lt;CODE&gt;OrderType = 'Historical'&lt;/CODE&gt; when navigating to those sheets.&lt;/LI&gt;
&lt;LI&gt;For Current Order sheets, add an action that applies a filter for &lt;CODE&gt;OrderType = 'Current'&lt;/CODE&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;HR /&gt;
&lt;H4&gt;&lt;STRONG&gt;Why This Approach Works Better:&lt;/STRONG&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Simplified Data Model&lt;/STRONG&gt;: Consolidating the tables removes the need for duplicated fields (&lt;CODE&gt;H_OrderNo&lt;/CODE&gt;, &lt;CODE&gt;OrderNo&lt;/CODE&gt;) and makes the app more maintainable.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Better Performance&lt;/STRONG&gt;: A single table is more efficient for Qlik Sense to process than two separate tables.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Improved User Experience&lt;/STRONG&gt;: Users won’t be confused by irrelevant filters carrying over between unrelated sheets, as the filters will now be applied dynamically based on the sheet context.&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;H4&gt;&lt;STRONG&gt;Recommendation:&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;While the direct approaches using bookmarks or splitting the app are feasible, consolidating the data model with a single table is the most robust and scalable solution. It aligns with best practices in Qlik Sense and reduces the overall complexity of the app.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2024 05:04:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2497813#M102783</guid>
      <dc:creator>nhenckel</dc:creator>
      <dc:date>2024-12-13T05:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: Want to clear the selection for the table From the sheet which is not using that field</title>
      <link>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2499336#M102973</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/79204"&gt;@nhenckel&lt;/a&gt;&amp;nbsp;Thanks for reply, We will check what we can use from above solution you have provided.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Dec 2024 05:45:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Want-to-clear-the-selection-for-the-table-From-the-sheet-which/m-p/2499336#M102973</guid>
      <dc:creator>Fenil</dc:creator>
      <dc:date>2024-12-26T05:45:35Z</dc:date>
    </item>
  </channel>
</rss>

