Changes to a standard API causing the Post-Procedure to NOT execute.

I have recently added changes to the SubscibeItemClass API to execute custom pre and post procedures and added new "custom" data tags to the API and have had the "standard" post procedure STOP executing.

I have added escapes to the ATC034 program at 101 & 201 and I am running the SMU954 program in an active session and the escape for 101 is hit while the escape at 201 is ignored. In addition to the escape being skipped the actual change of the item class description is not happening.

Has anyone found a situation that would cause the standard post-procedure to not execute as expected? I have copied both the standard and custom values from the API entry program and pasted them into a workspace then "performed" those pasted values and hit the escape as expected (so that eliminates - in my mind anyway, that the problem is a mis-typed procedure).

Bob Fitzgibbon

Attachment_4280.zip

Find more posts tagged with

Comments

Legacy Contributor

Bob,

I could be wrong, but I think this is by design, at least for an "Other" type request, because typically the post procedure is used to return a complete xml response. The custom procedure wouldn't be able to properly adjust the standard response, so the custom procedure runs instead of the standard procedure. The driver likely doesn't know that an update, as opposed to a response, is taking place. Simply perform the standard procedure as the first thing in your custom procedure. I trust Tim will correct me if I'm mistaken.

Legacy Contributor

I would check the custom data tags to make sure they have been setup correctly. I have found that while parsing them, if there is a problem, the API will not process the standard or custom post procs. Under normal circumstances, both will be processed.

Also, I seem to remember that when I have caused problems with the API, the error shows up in a log somewhere. I haven't gotten errors recently, but it might be in the 'xmllog' directory in the base install directory. I am not positive, but I think that is where it is. It also might just be in the "output" xml document in the api/out directory. You might also check *web/runbg_error.log

If none of that helps, try entering an 'Err Rcvr-Proc' procedure in API Entry for SubscribeItemClass and put an escape in there. Then run SMU954 from a code screen. When the error occurs, at least it will escape shortly after the error occurred and do some troubleshooting. Print MESSAGE$

Good Luck...

Eddy Vittini

Jason,

Thanks for the insights... I thought I had checked each of the procedures in the API new records that I added, but I mistyped one of them and your idea on the 'Err Rcvr-Proc' helped with the error 55 in SMU995 on line 6230.

Copyright © 2025 Infor. All rights reserved.