Home Forums PrintNode Connector Report with TransactionType Browse

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • Bernhard KloibmüllerBernhard Kloibmüller
      Post count: 7


      We encountered a problem with this app with reports where the TransactionType is set to Browse.

      We even cannot preview a report with this TransactionType.


      “IWX PrintNode API Mgt.”(CodeUnit 70097842).setPaperTrayForReport – Insight Works PrintNode Connector by Insight Works
      ReportManagement(CodeUnit 44).OnAfterGetPaperTrayForReport line 2 – Base Application by Microsoft
      ReportManagement(CodeUnit 44).GetPaperTrayForReport line 2 – Base Application by Microsoft
      “Reporting Triggers”(CodeUnit 2000000005).GetPaperTrayForReport line 2

      Even a ProvessingOnly report ist causing this issue!

      My version: <span id=”bvuee” class=”clickablestringcontrol thm-cont-u1-font-size-2–minflat thm-cont-u1-font-stack-2–minflat thm-cont-u1-color-2–minflat thm-cont-g2-bgcolor-2″>Version: AT Business Central 17.2 (Plattform 17.0.19353.20794 + Anwendung 17.2.19367.19525)</span>


      Best Regars


      • This topic was modified 3 years, 4 months ago by Bernhard KloibmüllerBernhard Kloibmüller.
      Travis PlettTravis Plett
        Post count: 132


        PrintNode Connector is made only for assigning specific printable report numbers to a printer:


        Browse type, preview and processing reports are not supported by PrintNode Connect as they are not intended for printing.


        PrintNode should not be used on a generic Printer Selection rule when a user want to browse, preview or use processing reports. You might be able to get that to work if you make exceptions rules for unprintable reports, but it was not designed for that and has not been tested.



        Bernhard KloibmüllerBernhard Kloibmüller
          Post count: 7


          Ok, we will try this. Thank you.

          I will give you feedback.

          Best Regards

          Bernhard Kloibmüller

          Bernhard KloibmüllerBernhard Kloibmüller
            Post count: 7

            My promised update:

            setting up the report 0 in the printer selection is not a good idea. When you do this my described problem occurs. I am not sure why but the system tries to apply the printer on a processing only report, so never set up a printer selection 0 for a default output.


            Thank you for the support

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.