This would be a lot easier with a restful crud api
And if I understand Bart’s novella on Epicor Functions, you’ll be able to do just that. Start planning your 10.2.500 upgrade!
1 Like
But that doesn’t let you skip understanding the basics, the BO’s, the tables, and the rest of the Epicor stuff. Functions just gives you a way to not have to repeat yourself. REST simply exposes the same stuff that’s already there, if you can’t do it with the tools in the system, you aren’t going to be able to do it with REST outside of the system (except for maybe so weird security type issues)
You’re right but at least all of the calls can be done in the function and then you expose the function endpoint to REST and get the CRUD we’re looking for. Hide all that implementation details.
1 Like
I have a background in web applications and have worked a lot with RESTful api’s. That’s what I’m used to doing. Still not fully up to date with Epicor but that’s why I keep doing and learning. Just stating an opinion
And I get that. Once you start needing stuff outside of epicor, you’re going to be way ahead of the game. But it doesn’t really let you skip any of the business rules, as the REST Api’s are just wrappers on the Epicor BO’s anyways, so you still need to know that to make it work.You’ll still need to be able to trace and replicate the flow that Epicor has in place, even with REST.
2 Likes