Skip to main content
Solved

Custom processing screen doesn't update progress until it is finished


darylbowman
Captain II
Forum|alt.badge.img+13

I have a few processing screens that I’ve created recently that I just noticed recently don’t update their progress until the processing is completely finished. For example, if I process 25 records, the progress bar will spin indeterminately with 25 ‘remaining’ until it has completely finished, and then all 25 will be ‘processed’.

This does not strike me as being normal behavior, but I wanted to check in to see if anyone else has experienced this or if I am doing something wrong. I am working with 22.209

Best answer by darylbowman

I finally discovered what the issue was. I think in some cases, processing statuses are updated automatically, but in this situation, I had to use PXProcessing.SetError() or PXProcessing.SetInfo() to update the processing status of each record.

After this change, it behaves entirely normally.

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

10 replies

aaghaei
Captain II
Forum|alt.badge.img+10
  • Captain II
  • 1205 replies
  • March 7, 2023

Just curious if you have Process Delegate Suppression properties like as SuppressUpdate or SuppressMerge or other suppressions on?


darylbowman
Captain II
Forum|alt.badge.img+13
  • Author
  • 1739 replies
  • March 7, 2023

Nope, wasn’t aware they existed.


aaghaei
Captain II
Forum|alt.badge.img+10
  • Captain II
  • 1205 replies
  • March 7, 2023

I just tested one of my custom processing screens and I have the same issue. I just updated my libraries to 22R2 last week.


darylbowman
Captain II
Forum|alt.badge.img+13
  • Author
  • 1739 replies
  • March 7, 2023

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • 648 replies
  • March 8, 2023

@darylbowman we’ll check


  • Acumatica Moderator
  • 3 replies
  • March 8, 2023

Hi @darylbowman , I have been able to reproduce the issue also on a custom processing screen (tested in 22.205).

 

I will report this issue to our engineering team. 


  • Acumatica Moderator
  • 3 replies
  • March 10, 2023

@darylbowman I tested it one more time, but with the processing taking longer than 5 seconds to complete (the time it takes to update the window), and it is working fine. Can you confirm how long does it take to complete the processing in your case ?

 


darylbowman
Captain II
Forum|alt.badge.img+13
  • Author
  • 1739 replies
  • Answer
  • May 9, 2023

I finally discovered what the issue was. I think in some cases, processing statuses are updated automatically, but in this situation, I had to use PXProcessing.SetError() or PXProcessing.SetInfo() to update the processing status of each record.

After this change, it behaves entirely normally.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2781 replies
  • May 9, 2023

Thank you for sharing your solution with the community @darylbowman !


Joe Schmucker
Captain II
Forum|alt.badge.img+2

I had the same issue.  Hence me being here right now.  I found that I was missing this line at the top of my processing method:

PXProcessing<ICSDiscountProgram>.SetCurrentItem(program);

By not setting the current item, it was just recycling the description of the first item in the processing list and not updating the counts.


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