<?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: Difference between Quick Selections and Qlik Sense Selection Model in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Difference-between-Quick-Selections-and-Qlik-Sense-Selection/m-p/1047730#M4366</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The standard selection model is well suited for most, if not all, charts, that is hypercube-based extensions. If you send selections straight to the engine in a chart, the chart will immediately update and show only the value you just selected, and it will be impossible to select multiple values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a listobject-based extension (like the Horizantal listbox example, where these different selection models are implemented) you could send selections immediately to the engine and still be able to select multiple values, since the extension shows also the unselected values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Erik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Feb 2016 07:16:23 GMT</pubDate>
    <dc:creator>ErikWetterberg</dc:creator>
    <dc:date>2016-02-05T07:16:23Z</dc:date>
    <item>
      <title>Difference between Quick Selections and Qlik Sense Selection Model</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Difference-between-Quick-Selections-and-Qlik-Sense-Selection/m-p/1047729#M4365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am new to Qlik Sense Extension Development. I wonder if anyone could explain the difference between the Qlik &lt;/P&gt;&lt;P&gt;Sense selection models.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The documentation says this about the selection models:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Standard &lt;SPAN class="PrimaryGenericName"&gt;Qlik Sense&lt;/SPAN&gt; selection model with toolbar and wrapper around the object supported by methods in the Extension API.&lt;/LI&gt;&lt;LI&gt;Quick selection, where selections are sent straight to the &lt;SPAN class="PrimaryEngineName"&gt;Qlik engine&lt;/SPAN&gt; and immediately are reflected in the object supported by methods in the Backend API.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;*&lt;A href="https://help.qlik.com/sense/2.1/en-US/developer/#../Subsystems/Platform/Content/Concepts/selections.htm%3FTocPath%3DQlik%2520Sense%2520platform%2520overview%7CConcepts%7C_____11" title="https://help.qlik.com/sense/2.1/en-US/developer/#../Subsystems/Platform/Content/Concepts/selections.htm%3FTocPath%3DQlik%2520Sense%2520platform%2520overview%7CConcepts%7C_____11"&gt;https://help.qlik.com/sense/2.1/en-US/developer/#../Subsystems/Platform/Content/Concepts/selections.htm%3FTocPath%3DQlik…&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apart from the fact that if I choose to use Qlik Sense Selection model I get to have a toolbar with clear(✕) and confirm(✔) buttons,&lt;/P&gt;&lt;P&gt;is there any situation where one model is better suited than the other ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why these two models exists ? Is it that the Standard Qlik Sense selection model just provides a "confirm button" ? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Feb 2016 07:45:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Difference-between-Quick-Selections-and-Qlik-Sense-Selection/m-p/1047729#M4365</guid>
      <dc:creator />
      <dc:date>2016-02-04T07:45:47Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between Quick Selections and Qlik Sense Selection Model</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Difference-between-Quick-Selections-and-Qlik-Sense-Selection/m-p/1047730#M4366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The standard selection model is well suited for most, if not all, charts, that is hypercube-based extensions. If you send selections straight to the engine in a chart, the chart will immediately update and show only the value you just selected, and it will be impossible to select multiple values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a listobject-based extension (like the Horizantal listbox example, where these different selection models are implemented) you could send selections immediately to the engine and still be able to select multiple values, since the extension shows also the unselected values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Erik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 07:16:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Difference-between-Quick-Selections-and-Qlik-Sense-Selection/m-p/1047730#M4366</guid>
      <dc:creator>ErikWetterberg</dc:creator>
      <dc:date>2016-02-05T07:16:23Z</dc:date>
    </item>
  </channel>
</rss>

