8 Replies Latest reply: Sep 20, 2017 10:35 AM by Ruggero Piccoli RSS

    NPrinting 17 - report fails via On Demand but not via Designer

    Kris Markee

      I have QV 12.10 SR 6 and NP 17.3.  I have On Demand in place and it worked fine with my pixel perfect report that had Levels in place using singled out fields (not a full table as the level) when my qvw was published to a mounted folder and I was using an internal url to access Access Point, but I had to publish it to the root folder of QlikView instead in order for the On Demand button to function and show the reports available to run from an external url (per Qlik there is a NP bug requiring this) and now that same report runs fine in NP Designer via Preview but errors out when called from On Demand, giving me the "wrong content node" error.  It's frustrating that NP Designer works but the On Demand route does not.  It appears to be related to levels in pixel perfect reports (or maybe all report types, I have yet to try it) because when I create a new report, leave out levels (and DetailReport band) it executes, but once I add a level (single field or a table) it errors via On Demand.  Does anyone have any experience or suggestions regarding this?  Thanks.

        • Re: NPrinting 17 - report fails via On Demand but not via Designer
          Ruggero Piccoli

          Hi,

           

          The error message "Wrong content node response type" can be caused by invalid applied filters or a cycle that try to select an invalid value for the field (a value that doesn't exist in the field).

          Example 1

          Your source contain the Year field that contains the values 2012, 2013 and 2014 but you added a filter with Year = 2015 to the report

          Example 2

          you added to the report the filter Year = 2014 and the Country field into the Levels node. Remember that adding a field in the Levels node is like a filter. When the report is created it is possible that a value of Country has an empty data set for the year selected. For example, thare are not sales in Italy in 2014. This generate the error you saw.

           

          We improved how this behaviour is managed in lates version and we are still working on it. So, first of all, upgrade your installation to September 2017 (or later when they will be available).

          Then check the applied filters.

           

           

          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.

          • Re: NPrinting 17 - report fails via On Demand but not via Designer
            Kris Markee

            I did confirm that it appears to affect all report types (I created an xls report), and the export type within On Demand does not make a difference either....still errors but NP Designer > Preview has no issues and renders everything I've tried so far.

              • Re: NPrinting 17 - report fails via On Demand but not via Designer
                Ruggero Piccoli

                Yes, it affected all report types because it is related with filters and not with the report type.

                 

                A preview with the Designer doesn't keep in care the cycles, so it could be that you added cycles and that the issue is generated because a value of a filed used in cycles cause an empty dataset in another filed used in filters or levels.

                  • Re: NPrinting 17 - report fails via On Demand but not via Designer
                    Kris Markee

                    Is what you are talking about in this thread related to filters on the report and/or using a single field as a level?  I ask because I don't have any filters and I have tried both a single field and my straight table as levels.  Thanks.

                      • Re: NPrinting 17 - report fails via On Demand but not via Designer
                        Ruggero Piccoli

                        My suggestions are:

                        - upgrade to September 2017 because this part was updated. It could be that with September 2017 you resolve

                        - to create a report with Levels, Pages or Cycles NPrinting will apply filters. So it could be that you have any filter but you still see the error, because, for example, you have a field/table in Levels that conflict with a Cycle

                        - you can try to create the report step-by-step and run it at every step to understand where the issue is generated

                        - if you cannot resolve I suggest to open a support ticket in order to investigate directly because the cause could be another.

                         

                        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.