No, I’m basing my conclusion on the fact that I still get the error below (like it’s being called from PO Receipt with the expected parameters in a different sequence). So, it must still think I’m still calling it from UD39.
Are you able to pass a JobNum in your parameters and have it show on the Material Tag “report”? I see it’s blank in your screenshot.
Hi Chris.
When I changed the line: ProcessCaller.LaunchForm(hacky, “Erp.UIRpt.MtlTags”,lfo); //to pass hacky instead of oTrans
…then I got the following 2 errors one right after the other:
Here’s my code around the call. Do you see anything else out of place?
Thanks, Sharla