NPrinting 17 - pixel perfect detail row totals - Qlik Community

kdmarkee · ‎2018-09-11

I am running QV 12 and NP April 2018. I have a pixel perfect report where my straight chart is being used as a level and I want to show the following, where there is a total for each patient in my detail band, and a total for the entire band. Can this be achieved? Thanks.

Ruggero_Piccoli · ‎2018-09-12

Hi,

Check this help site page https://help.qlik.com/en-US/nprinting/June2018/Content/PixelPerfectReports/Add-Totals-Subtotals.htm

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.

kdmarkee · ‎2018-09-13

I was hoping there was another alternative as this doesn't seem feasible when you have a hundreds or thousands of values that the level has to rip through in a "level with sublevel" scenario, as I am finding that performance is horrible with my testing. I guess I'll have to come up with another alternative for this report and hope the user won't mind. Thanks.

Ruggero_Piccoli · ‎2018-09-14

Hi,

Using level and sublevels could be slow in case you have many rows.

If you have a so high quantity of rows to export maybe it is better to create an Excel report and export them ad tables (add them in the Excel template Tables node). A table is exported in a single step, a level is exported row by row so a table is faster to be exported.

Of course an Excel report could be difficult to be rendered in PDF format.

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.

kdmarkee · ‎2018-09-17

Yeah, I have been experimenting with an Excel solution. Thanks for the ideas.

kdmarkee · ‎2018-09-28

Is it possible to add the patient total as a column without adding a column to my QV chart? (I would suppress repeating values in NP) I'm not sure if I can leverage NP to generate the Patient Total column

Ruggero_Piccoli · ‎2018-10-01

Hi,

As you did for the main level. I suppose you are using nested levels, so add a Group Footer for each nested level, drag and drop the field you want to calculate the total and set the totals calculation properties. PixelPerfect is able to separete levels and sublevels without the need of a new column in the source app.

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.

kdmarkee · ‎2018-10-01

No, I actually want to abandon the nested level because report performance is poor, so instead I wanted to create a total on the row as the main data. Sorry if my second image wasn't clear on that point. I'm guessing I would have to build this in my QV chart since it doesn't seem like I can do the summation I need in my detail band.

Ruggero_Piccoli · ‎2018-10-02

Hi,

I never tried without levels and sublevels. I have to investigate if there is an alternative.

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.