<?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: Nprinting connection Reload metadata query in Qlik NPrinting</title>
    <link>https://community.qlik.com/t5/Qlik-NPrinting/Nprinting-connection-Reload-metadata-query/m-p/1926852#M35948</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please avoid to cross-post the same question multiple time in the community. Thanks.&lt;/P&gt;
&lt;P&gt;You have to reload the connection caches every time you changed something in the connected QlikView documents or Qlik sense app so Qlik NPrinting will record the changes.&lt;/P&gt;
&lt;P&gt;You have to reload the caches of QlikView local connections after every QlikView document data reload to force the closure of all opened documents otherwise you will get report with not updated data. I suggest to do the same also with QlikView Server connections.&lt;/P&gt;
&lt;P&gt;It it not needed to reload connection caches of Qlik Sense connection if you did only a data reload.&lt;/P&gt;
&lt;P&gt;Connection cache reloads can be triggered on a time basis or launched via APIs.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Ruggero&lt;/P&gt;</description>
    <pubDate>Thu, 05 May 2022 12:07:03 GMT</pubDate>
    <dc:creator>Ruggero_Piccoli</dc:creator>
    <dc:date>2022-05-05T12:07:03Z</dc:date>
    <item>
      <title>Nprinting connection Reload metadata query</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Nprinting-connection-Reload-metadata-query/m-p/1926774#M35945</link>
      <description>&lt;P&gt;The usual sequence for any Nprinting scheduled publish task is:&lt;/P&gt;
&lt;P&gt;1] Reload Source QlikView or Qliksense App.&lt;/P&gt;
&lt;P&gt;2] Reload metadata of associated connection(Only for the first time setup)&lt;/P&gt;
&lt;P&gt;3] Run Nprinting Publish task after successful reload of source app.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do we need to schedule The metadata reload of Associated connection always before running the publish task&lt;/P&gt;
&lt;P&gt;Under what circumstances we should reload the metedata of any Nprinting connection before the publish task?&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 10:06:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Nprinting-connection-Reload-metadata-query/m-p/1926774#M35945</guid>
      <dc:creator>TusharDev_Qlik</dc:creator>
      <dc:date>2022-05-05T10:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: Nprinting connection Reload metadata query</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/Nprinting-connection-Reload-metadata-query/m-p/1926852#M35948</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please avoid to cross-post the same question multiple time in the community. Thanks.&lt;/P&gt;
&lt;P&gt;You have to reload the connection caches every time you changed something in the connected QlikView documents or Qlik sense app so Qlik NPrinting will record the changes.&lt;/P&gt;
&lt;P&gt;You have to reload the caches of QlikView local connections after every QlikView document data reload to force the closure of all opened documents otherwise you will get report with not updated data. I suggest to do the same also with QlikView Server connections.&lt;/P&gt;
&lt;P&gt;It it not needed to reload connection caches of Qlik Sense connection if you did only a data reload.&lt;/P&gt;
&lt;P&gt;Connection cache reloads can be triggered on a time basis or launched via APIs.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Ruggero&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 12:07:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/Nprinting-connection-Reload-metadata-query/m-p/1926852#M35948</guid>
      <dc:creator>Ruggero_Piccoli</dc:creator>
      <dc:date>2022-05-05T12:07:03Z</dc:date>
    </item>
  </channel>
</rss>

