<?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>idea NPrinting  Always One Selected Value support in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idi-p/1849325</link>
    <description>&lt;P&gt;Quite a basic one here - NPrinting should support changing values within "Always One Selected Value" fields, which for some reason it does not.&lt;/P&gt;
&lt;P&gt;Qlik currently suggests making a copy of every app that uses "Only one selected" and then maintaining two copies of each app, but this&amp;nbsp; is not a feasible solution.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Oct 2021 10:03:06 GMT</pubDate>
    <dc:creator>Or</dc:creator>
    <dc:date>2021-10-20T10:03:06Z</dc:date>
    <item>
      <title>Re: NPrinting  Always One Selected Value support</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idc-p/1865779#M7957</link>
      <description>&lt;P&gt;Agree, that would be a great game-changer.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Dec 2021 03:09:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idc-p/1865779#M7957</guid>
      <dc:creator>Lech_Miszkiewicz</dc:creator>
      <dc:date>2021-12-02T03:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: NPrinting  Always One Selected Value support</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idc-p/1865946#M7964</link>
      <description>&lt;P&gt;I'm no expert on how NPrinting works under the hood, but my understanding of this limitation is that it is because the actual steps taken for a filter are either:&lt;/P&gt;
&lt;P&gt;* Select the values required (if they are possible), or&lt;/P&gt;
&lt;P&gt;* Clear the field and then select the values required (if they are possible), if override has been selected&lt;/P&gt;
&lt;P&gt;And as a result, Always One Selected does not work because the values are never possible (as the one original value remains selected through a clear field).&lt;/P&gt;
&lt;P&gt;Perhaps this could be worked around by adding a third checkbox, "Always one selected value", which would tell NPrinting to pass certain filters through the app URL or through whatever other mechanism might be usable to avoid this catch?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Dec 2021 10:49:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idc-p/1865946#M7964</guid>
      <dc:creator>Or</dc:creator>
      <dc:date>2021-12-02T10:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: NPrinting  Always One Selected Value support - Status changed to: Closed - Declined</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idc-p/2015635#M11294</link>
      <description>&lt;P&gt;Thank you for the post. This is as per documentation (as you already know).&amp;nbsp; Closing this idea as there is no plan to resolve this at this point in time.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2022 20:07:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/NPrinting-Always-One-Selected-Value-support/idc-p/2015635#M11294</guid>
      <dc:creator>Andrew_Kruger</dc:creator>
      <dc:date>2022-12-12T20:07:58Z</dc:date>
    </item>
  </channel>
</rss>

