Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Announcements
BI & Data Trends 2021. Discover the top 10 trends emerging in today. Join us on Dec. 8th REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Specialist
Specialist

When should you Reload Metadata?

Hi,

I am a bit confused about circumstances in which metadata should be reloaded.

I know metadata should be reloaded when you have new objects in a QlikView document that you want to use in NPrinting.

But what about when you have made changes to expressions of existing objects?

Or if you have added new variables?

If a connection is based on a QVP connection, should metadata be reloaded when you want to reflect new data? The QlikView Server automatically performs a reload and the NPrinting report is supposed to run after so not sure in this.

What other circumstances should you reload metadata? And does is differ for Qlik Sense and QlikView (please go into detail what those differences are)?

1 Solution

Accepted Solutions
Highlighted

Hi John,

There is no clear answer to your question. It really all depends on how you have setup your environment. In my environments i ALWAYS have separate application only for NPrinting reports. Therefore any change to this application in my opinion should also require metadata reload. This makes it quite simple and straightforward for me.

So:

  • any new object (expression, dimension, variable)
  • any new chart
  • any change to existing objects
  • any change in existing sheets
  • added or removed fields tables from data model

I always reload metadata after doing one from the above. I know that in some cases this is maybe not necessary (for example if change a expression which calculates a value in a table) , but i do it just to have everything always up to date.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.

View solution in original post

14 Replies
Highlighted
Champion III
Champion III

Hi

https://help.qlik.com/en-US/nprinting/February2018/Content/GettingStarted/HowCreateConnections/Reloa...

Connection metadata contains information about the data and structures of linked QlikView documents or Qlik Sense apps.

Qlik NPrinting automatically uploads metadata when a new connection is created. Metadata must also be updated whenever you change the data structure or content of QlikView documents or Qlik Sense apps connected to Qlik NPrinting. This ensures that Qlik NPrinting is aware of these changes.

After the metadata is reloaded, all instances of QV.exe that are running on Qlik NPrinting Engines associated with the connection will automatically stop and restart to update them. Existing reports are not automatically re-run, so they may contain old data. Reports executed after a metadata reload will show the updated data.

Highlighted
Champion III
Champion III

yes

the data that is getting refreshed in Qlikview document from  Qlikview server is also getting fetched continuously by the NPrinting Server through qvp connection and so there is no need of reloading the metadata.

Highlighted

Hi John,

There is no clear answer to your question. It really all depends on how you have setup your environment. In my environments i ALWAYS have separate application only for NPrinting reports. Therefore any change to this application in my opinion should also require metadata reload. This makes it quite simple and straightforward for me.

So:

  • any new object (expression, dimension, variable)
  • any new chart
  • any change to existing objects
  • any change in existing sheets
  • added or removed fields tables from data model

I always reload metadata after doing one from the above. I know that in some cases this is maybe not necessary (for example if change a expression which calculates a value in a table) , but i do it just to have everything always up to date.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.

View solution in original post

Highlighted
Employee
Employee

Hi,

I would to add that you need to reload metadata also every time you update a QlikView document if you created a local connection to it. Of course, we suggest to use server connections instead of local.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Highlighted
Master III
Master III

Hi Ruggero,

Just wanted to confirm that Metadata reload is only needed if Front-end is changed(Chart objects used in the NPrinting report), Data refresh in QS App doesn't require meta data reload, right?

Highlighted

In general YES - you are correct.

1 exception though; just to clarify:

on the back-end you might have some variables defined like:

Let vToday = Date(today(),'YYYY-MM-DD');

lets assume you change this to

Let vToday = Date(today(),'DD-MMM-YY');

Although it is a back-end change i would still reload metadata.

New data coming to Qlik Sense fields/tables does not require metadata reload!

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Highlighted
Creator
Creator

I have a problem. I trigger a NPrinting publish task from inside a Qlik Sense app data load script. And in the report, I use a variable. This variable changes with every Qlik Sense data reload. This reload runs every minute.

So every minute the Qlik Sense app reload sets a new value to the Qlik Sense variable and triggers the NPrinting publish task. The task is rendering a report with that variable inside.

The problem is, every new report displays the variable value of the previous reload. But normally NPrinting should fetch the new variable value. Or do I need to reload every time the meta data of the connection?

When does NPrinting look for the new variable values?

Highlighted

Hi Christoph

I think your problem is different than this topic subject so maybe create your own one.

you are saying that:

So every minute the Qlik Sense app reload sets a new value to the Qlik Sense variable and triggers the NPrinting publish task. The task is rendering a report with that variable inside.

so if you are triggering NPrinting task from the same script of the application you use for NPrinting you are making big mistake. Your app will not get saved and NPrinitng runs of previously saved app.

You should have 2 Qlik sense apps reloading one after another.

  • 1 st reloading Qlik Sense app
  • 2 nd triggering NPrinting task

We can discuss more in dedicated topic.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Highlighted
Employee
Employee

Hi,

I think you should schedule a metadata reload to force connections to be closed and reopened. In this way the updated value of variables will be used.

Do a test, please.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.