Hopefully I can find someone here who can help as I’ve looked everywhere! My service connect workflow is working great. Basically, it is an Auto Issue Job Material workflow from a dashboard dump to Excel, edit some required data, save to csv and drop to a shared folder. My problem is with the labels. No matter what I place in for data definition, style num, style description, etc., it will ONLY print to the default report style and ONLY to ReportID IssAssmInvMvm. Is there a flag to set to logical that tells SC to honor the label that I actually want?
Yes I absolutely am but it ignores my data definition/report style and only prints to the one I mentioned. Now, if I add my report style to the above report and make it default, it will then print to the label I need. However, this changes the label that Issue Material prints to. Unless I am not setting some sort of flag somewhere…
This is prior to the above screen capture. It shows that it is pulling the default parameters prior to getting the new parameters. This is the label that it prints to unless I set mine to default.
I am unsure on how to write a BPM to get the parameters. I looked in Method Directives on Issue Return but it doesn’t seem that I can get past the PerformMaterialMovement BO… I don’t know how to get into InventoryMovement.Epicor.Mfg.Rpt.InventoryMovement.GetNewParameters… Doesn’t seem possible.
How exactly are you generating/modifying the print params? You should run a trace as you are generating/changing report parms in the UI and see what additional helper methods are being called.
PreGetNewParameters Conversion (gets the default parameters)
GetNewParameters call
SetPrintingProperties conversion where I set the printer name, printer properties, label style, etc. (supposed to set the new parameters)
And then pass to SubmitToAgent
If you do a trace on UI of changing report parms (particularly report style or def) do you see anything between GetNew/GetDefault and the SubmitToAgent?
Silly question - On your conversion where you set params, you do have that routed to the output right?
In my experience with some of these odd behaviours in ESC look closely that there is not some method that looks very similar to the one in the trace, (eg addnewlabor) or you have set the rowmod correctly, sometimes I have seen the rowmod not being set in the trace, but in the workflow you need to set it, particularly where you replace the update method with updateext.
Is it possible you have missed linking a result to a request, or are you using a process variable to store you report parameters?