Application Studio vs BPM

[josecgomez]

@jsmuland

Just want a sanity check if there is a best practice here.

I mean I’m not the dictator of best practices but I am certainly well opinionated on the topic (almost any topic just ask @jgiese.wci and @Banderson ).

I would say if you can avoid making BO calls on AppStudio then do.

@jsmuland

I am not down with functions yet.

Get into them, they are the best thing that Epicor has given us in years.

I will almost never make BO calls in App Studio. Move all your calls to functions and BPMs, move all your logic to the back end. I just posted this on another topic but frankly it applies for this too so I won’t repeat myself I’ll point you in that direction instead

IssueReturn PerformMaterialMovement REST call not showing in PartTran

As @Mark_Wonsil always says I would highly recommend you write a function that will take the 2 or 3 parameters you actually need and do the Issue Return from there server side thus abstracting the complexity. Abstracting complex logic into a server-side function has several advantages over directly hitting complex endpoints from the client: Simplified Client Code: By abstracting the logic, your client code becomes much simpler. You can encapsulate all the intricate details and business rules…