Skip to main content
Solved

GETTING ERROR WHILE PROCESSING PRINT FROM CUSTOM PROCESSING SCREEN

  • February 25, 2022
  • 3 replies
  • 254 views

Prosun48

I have created a Processing screen, To process EMAIL and PRINT of multiple Payment and Application documents.

While Processing PRINT I am getting the following ERROR.

 

The Screen ID showing in the error message is the report screen ID which should pop up to print the report. but the Report is not popping up.

 

Following is my code :

 

We are getting error in line no 72, throw ex;

 

I am unable to find out where I am going wrong,

Thanks In Advance.

Best answer by darylbowman

PXReportRequiredException is fancy version of PXException. Throwing any form of PXException in a long running operation will cause it to fail (as far as I know) unless you run the PXLongOperation inside of a try / catch statement and handle it. Since this doesn’t seem like the best solution in your case, I’d recommend trying a different approach.

 

 

View original
Did this topic help you find an answer to your question?

3 replies

Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3410 replies
  • February 25, 2022

Hi, @Prosun48  Since you are working with the Combined Reports, can you please review the below links, which may help you.

https://stackoverflow.com/questions/6029142/merging-multiple-pdfs-using-itextsharp-in-c-net

 


deebhane
Semi-Pro I
Forum|alt.badge.img+1
  • Semi-Pro I
  • 62 replies
  • February 25, 2022

hi @Prosun48 ,

To my thought, since the processing screen in-built has a Long run mechanism  and your logic is executing inside the long run operation you cannot open a popup message after process is completed. Rather you need to try downloading the report programmatically.  

Please reference the below link for reference. 

acumatica - Generate Report Programmatically - Stack Overflow


darylbowman
Captain II
Forum|alt.badge.img+13
  • 1716 replies
  • Answer
  • February 25, 2022

PXReportRequiredException is fancy version of PXException. Throwing any form of PXException in a long running operation will cause it to fail (as far as I know) unless you run the PXLongOperation inside of a try / catch statement and handle it. Since this doesn’t seem like the best solution in your case, I’d recommend trying a different approach.

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings