Change "Closed" status on "Balanced" for Checks and Payments Item programmatically

Unfortunately that error doesn’t give much information, just that something that the method was trying to reference was null. It’s not an error I’ve come across before. You can unpublish your customizations and then republish one by one to figure out which one is causing it though.

I cancelled all customization projects but it did not help

Is there any chance to reload this button in endpoint ?

At this point you just need to do some standard debugging to figure out what is causing the issue. It would seem that something is attempting to set that field to a null value(trying to cast null as a non-nullable decimal would cause that error) . I would try and figure out where in the ReverseApplication method is triggering the event handler and track the value of that field.

You would want to catch the event handler using a breakpoint. You would step through the ReverseApplication method line by line and see where it is triggering that event handler. You shouldn’t need to debug the file in your screenshot. Some values will be optimized away and not available to read. 

Hi @Naveen Boga 

I am trying to implement logic that we discussed, unfortunately, payment is not being removed from hold when this code is executed,

 string referenceNbr = "001985";
                APPaymentEntry graph = PXGraph.CreateInstance<APPaymentEntry>();
                graph.Document.Current = graph.Document.Search<APPayment.refNbr>(referenceNbr);
                graph.UnattendedMode = false;
                try
                {
                    graph.voidCheck.Press();
                }
                catch (PXRedirectRequiredException) { }
                // graph.Document.Current.Status = "B";
                graph.putOnHold.Press();
                graph.releaseFromHold.Press();

However, it worked for several items, for example : 001987 and 001986 were void via code if I missed part with removing from hold

But it did not worked for item 001985, can you suggest what is wrong with my code ?

Hi @Ivan  Once you click on the VOID, it will create a new VOIDED CHECK type of document against CHECK document and once you RELEASE it, the status will be changed to CLOSED

 

now it looks real it implement, I checked void option, all data is saved after void action

Firstly it makes “Hold” status 

After that I can remove it from hold

is it possible to call Void and remove Hold status programmatically ?

@Naveen Boga 

In previous comment where I replied to markusray17 I described that I need it to call from code that is called by Acumatica Automation Schedule that will open folder and check files which will have list of Checks and Payment Items that must be returned to Open status. I think it will not be available to call Base graph and there should be list of parameters for Void methods where I define which Item to process ( For example send ReferenceNbr to parameters in method)

Hi @markusray17 

Can you provide help with this part :

“if you are making a process screen you will likely want to use PXGraph.CreateInstance to get an instance of the APPaymentEntry graph. You can then set the current document to whatever APPayment you are handling and invoke the necessary actions. ”

I wrote the following way, where I send to graph instance ReferenceNbr of item that must be Voided

 string referenceNbr = "023675";
                APInvoiceEntry graph = PXGraph.CreateInstance<APInvoiceEntry>();
                graph.Document.Current = graph.Document.Search<APInvoice.refNbr>(referenceNbr);
                graph.ReverseApplication();

That is how it should be done, firstly I send reference Nbe to instance and after that I call the action, right ?