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.
Interesting - the calling dialog shows the proper form name now:
Note: I simply changed this line:
ProcessCaller.LaunchForm(hacky, “Erp.UIRpt.MtlTags”,lfo); //to pass hacky instead of oTrans
Also notice how my rev/bin/wh is skewed? Cuz you shouldnt have this:
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
private void btnPrintTag_Click(object sender, System.EventArgs args)
{
Hack hacky = new Hack();
LaunchFormOptions LaunchFormOpts = new LaunchFormOptions();
LaunchFormOpts.Sender = hacky;
string currentVal = getParametersForMtlTags();
LaunchFormOpts.ValueIn = currentVal;
ProcessCaller.LaunchForm(hacky, "Erp.UIRpt.MtlTags", LaunchFormOpts);
}
You need to be using the other one I made, as it returns a session (FornImpersonator).
When you create it, you’ll pass it the formname and oTrans
Got it! Thank you for sticking with me Chris! You’re awesome!!!
-Sharla
Excellent - mark the appropriate post as the solution if you would please