Handling Dataset in Function Maintenance

This may have already been asked and answered, but I’m not finding anything that addresses the issue directly.

When using Function Maintenance (FM), and attempting to follow Epicor’s no-code/low-code philosophy, I am running into an issue with moving data from one business object call to the next. When I call FreightService BuildMasterPackFreightRequest, I am passed back a tableset (which works quite well with the supplied widgets in FM). Moving further along the required steps to stage a master pack, I call FreightService FreightCarton. This asks for and returns datasets. Up to this point, all work has been done with tablesets. Then suddenly they spring the requirement of having a dataset formatted to call the business object and receiving a dataset after the call. I don’t see how to access the dataset with FM widgets to get the data from the returned tableset of the previous call to the required dataset for the FreightCarton call.

I’m sure this can be handled by manually building a conversion, but I really am trying to honor Epicor’s no-code/low-code philosophy where possible.

Thanks

Ivan Wright

Sometimes you just gotta do what you gotta do.

Functions themselves can be good candidates to keep your main bpm in widget land,
but break out more complex things into manageable chunks. Ie, call a function from widgets.

2 Likes