Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
bkozisek5r
Contributor III
Contributor III

HTML Report not Consistently Generating

I'm new to using Nprinting to generate automated reports, so thank you for your help in advance. 

I am using Nprinting November 2017 and i have an html report built that is then filtered by location in the publish task.  However when the publish task is generated i'm getting inconsistent results.  There are 4 tables in the HML report and when generated some tables won't render.  The next time all tables or different tables may render.   I can run the same publish task a number of times in a row and it will generate different results.  

 

Any suggestions?  This is really frustrating for the end users as they may or may not get an accurate report.

1 Solution

Accepted Solutions
Frank_S
Support
Support

Yes! always one location selected likely is causing this.

Always one selected is not supported.
There is no API call NP can send to either QlikView or Qlik Sense to override such selections.
See the following for details about unsupported items and how to work around this.
https://qliksupport.force.com/articles/000026081
https://qliksupport.force.com/articles/000038863

Hope this helps
Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!

View solution in original post

6 Replies
Frank_S
Support
Support

I suggest that you upgrade to the latest release of NPrinting for two reasons
1. To leverage the latest internal logging which which give greater insight into any filters that could cause varying results from user to user
2. From April 2018 and forward, you can enable invalid charts in your reports which will allow a report to generate even if there is an empty chart due to a filter conflict so some other issue.
If you have a 'location' filter as a task filter and if it is also used elsewhere ie: perhaps on the report or as a user filter, this will cause unpredictable report results due to filters cancelling eachother out.
For filter rules see: https://help.qlik.com/en-US/nprinting/September2018/Content/NPrinting/ReportsDevelopment/Static-dyna...

Finally, it's not clear here if you have QlikView or Qlik Sense you need to ensure that you do not have any unsupported items in your QVW (QlikView) document or QVF (Qlik Sense) application.

See the following supporting articles for more info.
QV unsupported items: https://qliksupport.force.com/articles/000026081
QS unsupported items: https://qliksupport.force.com/articles/000038863

Hope this helps.

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
bkozisek5r
Contributor III
Contributor III
Author

I apologize I am connected to QlikView and the report and all objects render successfully and properly some of the time, however the next morning when the same report/filter/users runs on the trigger it may only render 2 or 3 of the 4 tables.

 

I will talk with my IT team in the morning and see what it will take to update to the newer version.

Thanks

bkozisek5r
Contributor III
Contributor III
Author

I have upgraded NP to November 2018, however i'm still seeing the same issue, I am still on Nov 2017  QlikView. 

The report will generate and send but not all tables will render even though the source application when filtered for the location is working properly.  I have the Location Filter set up on the publish task. Below are a couple screen shots of the same publish task (location location filter) email generated just minutes apart (no change to application or meta data) but you can see that in one email the tables are missing and then the next they are populated and data visible.  

 

Thanks for the helpMissing Tables_LI.jpgTables Render_LI.jpg

 

Frank_S
Support
Support

If you have used a filter on the publish task and used the same dimension as a filter elsewhere ie: as a report filter, user filter, level, page, cycle, then this is what is likely causing you the issue.

You cannot use the same dimension twice in the same task. ie: you cannot use say Paris - City dimension as a report filter and Madrid - City dimension as a task filter. You will get empty set errors in the log and the report will not output as expected.

Filters Priority and Behavior:

  • Task Processing order: Publish Task, User Filters, Reports, Cycles, Pages, Levels, Object Filters (within a report template)
  • NOTE: You can NOT use the same dimension twice within the processing order shown above as doing so will result in an ‘Empty Set’ error message in the logs. This is due to Verify Filter Enforcement which is built into NP 17 and higher versions. This prevents invalid output from appearing.
Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
bkozisek5r
Contributor III
Contributor III
Author

The only place i have the filter applied is at the Publish Task Level.  I have tried creating an additional report with the filter applied at this level and no filter applied at the Publish level, but still resulted in the same inconsistent output, no user level filters are applied at this time.  

 

If the base application requires that there is always one location selected could this create the inconsistency?  If so, is there a solution to this as in the base application we don't want the end user to be able to select more than one location at a time.

Thanks for the help.

Frank_S
Support
Support

Yes! always one location selected likely is causing this.

Always one selected is not supported.
There is no API call NP can send to either QlikView or Qlik Sense to override such selections.
See the following for details about unsupported items and how to work around this.
https://qliksupport.force.com/articles/000026081
https://qliksupport.force.com/articles/000038863

Hope this helps
Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!