<?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: Paging metada in Qlik NPrinting</title>
    <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548279#M22706</link>
    <description>&lt;P&gt;Well,&lt;/P&gt;&lt;P&gt;short answer is:&lt;/P&gt;&lt;P&gt;* Fields (!!! not calculated dimensions !!!)&lt;/P&gt;&lt;P&gt;* Straight Tables - this would be for pages which would require combination of multiple fields you would use as a Page level.&lt;/P&gt;&lt;P&gt;Why - because you can only "cycle through" combinations of values from your application based on those 2 above mentioned entities. Reason? - Page (and similarly Level) "i think" is applied as a filter/selection when report is generated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Lech&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 23 Feb 2019 03:24:07 GMT</pubDate>
    <dc:creator>Lech_Miszkiewicz</dc:creator>
    <dc:date>2019-02-23T03:24:07Z</dc:date>
    <item>
      <title>Paging metada</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548272#M22705</link>
      <description>Can someone tell me how nprinting decides to pull object metadata on paging? As in, what objects can be used for paging and why?</description>
      <pubDate>Sat, 16 Nov 2024 04:21:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548272#M22705</guid>
      <dc:creator>mgranillo</dc:creator>
      <dc:date>2024-11-16T04:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Paging metada</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548279#M22706</link>
      <description>&lt;P&gt;Well,&lt;/P&gt;&lt;P&gt;short answer is:&lt;/P&gt;&lt;P&gt;* Fields (!!! not calculated dimensions !!!)&lt;/P&gt;&lt;P&gt;* Straight Tables - this would be for pages which would require combination of multiple fields you would use as a Page level.&lt;/P&gt;&lt;P&gt;Why - because you can only "cycle through" combinations of values from your application based on those 2 above mentioned entities. Reason? - Page (and similarly Level) "i think" is applied as a filter/selection when report is generated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Lech&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Feb 2019 03:24:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548279#M22706</guid>
      <dc:creator>Lech_Miszkiewicz</dc:creator>
      <dc:date>2019-02-23T03:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: Paging metada</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548281#M22707</link>
      <description>Straight table is a Qlikview object. Do you know about Sense? Is there a straight table equivalent that behaves the same in Sense? I tested the Sense table chart and Nprinting would pull metadata only if there was 1 dimension in the table. Oddly, my heatmap extension with 2 dimensions pulled in. So I'm left confused as to how it works.&lt;BR /&gt;&lt;BR /&gt;I need the straight table functionality of paging over multiple fields but Sense doesn't have this object. I suppose I have a work around with my heatmap extension but I would still like to know how it works for maintenance purposes.</description>
      <pubDate>Sat, 23 Feb 2019 03:36:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548281#M22707</guid>
      <dc:creator>mgranillo</dc:creator>
      <dc:date>2019-02-23T03:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: Paging metada</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548284#M22708</link>
      <description>&lt;P&gt;Yes it does. "Table Object" is a straight table object equivelent and will work as a Page. Keep in mind what i said about "Calculated dimensions". Make sure that your dimensions in the Qlik Sense Table (aka Straight table as it is not a Pivot Table &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; ) &lt;STRONG&gt;does NOT start wit "=" sign&lt;/STRONG&gt;, which would make it calculated dimension/expression and disqualify from use in Page/Level.&lt;/P&gt;&lt;P&gt;Also make sure you &lt;STRONG&gt;do not have conditional hide/show&lt;/STRONG&gt; on the columns (depending on QS version you are using it might be available).&amp;nbsp;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Lech&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Feb 2019 03:48:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548284#M22708</guid>
      <dc:creator>Lech_Miszkiewicz</dc:creator>
      <dc:date>2019-02-23T03:48:42Z</dc:date>
    </item>
    <item>
      <title>Re: Paging metada</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548285#M22709</link>
      <description>&lt;P&gt;Works perfectly now.&amp;nbsp; I had equal signs my dimensions. Thanks so much.&amp;nbsp; Extremely helpful. Qlik Support told me this was not supported functionality.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Feb 2019 04:08:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548285#M22709</guid>
      <dc:creator>mgranillo</dc:creator>
      <dc:date>2019-02-23T04:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: Paging metada</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548287#M22710</link>
      <description>&lt;P&gt;Awesome - glad i could help!&lt;/P&gt;</description>
      <pubDate>Sat, 23 Feb 2019 04:14:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Paging-metada/m-p/1548287#M22710</guid>
      <dc:creator>Lech_Miszkiewicz</dc:creator>
      <dc:date>2019-02-23T04:14:31Z</dc:date>
    </item>
  </channel>
</rss>

