I have been tasked with looking at some solutions for an integration between Lightsource (a product sourcing platform to get bids/quotes from Suppliers) and Epicor. We are currently on version 10.2.700, and want to get something in place before we do the 2025.2 upgrade. We were thinking of an integration tool like Jitterbit as a possible solution, but I wanted to ask the community if you have experience with anything for helping accomplish this task. From what I know, Automation Studio is not available for our current version, so that is not a current solution for us, though that may change once we finish the upgrade.
Maybe you can reach out to Workato directly as Automation Studio is just rebadged/repacked version with Epicor’s built connector. 10.2.700 has REST API and you could just write you own REST calls into Epicor.
1 Like
We used Jitterbit before Epicor moved to Automation Studio. I liked the platform and it worked for many years.
As @Randy said Automation Studio would work with if you did your own REST calls.
I’m not sure if they will sell it to you though. Even though you’re on an unsupported version, you’re still an Epicor customer.
1 Like
just more info, but Zapier is a good alternative and inexpensive. same rules apply, you’ll have to do your own API call creation but I did make it work before we upgrade to Automation Studio.
But I’m curious about LightSource - I need my vendors to do the same and was going to embark on that project in the new year - thanks for the suggestion - can I ask why that product?
1 Like
Procurement came up with them as their preferred solution. I do not really know what went into that decision, sorry.
1 Like
10.2.700 has Functions which is all you need for almost any kind of integration, in my opinion.
In general there are 2 approaches to integrations.
-
Code it all up yourself. Before Functions, people would write their own middleware programs, c# apps, custom DLLs, etc.. But now basically everything can be done inside Epicor Functions, which is a huge advantage.
-
Use an integrations platform/service. First there was Service Connect, and then Jitterbit, and now it’s Automation Studio.
There are pros and cons to each.
But if you want to use a platform, I’d push hard to try to use Automation Studio somehow as Randy suggested, because Jitterbit is old news and you really want to avoid a fresh implementation of old news. I still have to maintain a bunch of legacy Service Connect that I can’t seem to get rid of and it’s a giant pain. Everything new that we’re doing is using Functions, but there’s still a lot of old workflows left to convert. These things tend to live way longer than you think they will.
1 Like