Classic Sunset and Service Connect

[Chan213419 (Jeremy Chance)]

Has there been any information on the Sunset’s impact on SC? Let’s say you have workflows that use DLLs. Wouldn’t the DLLs no longer be accessible? Is anyone else concerned or addressing this or is it a wait and see type thing? Just curious to see what others are doing (or not doing )

[Chris_Conn]

If they are still supporting all of the DLLs to run the classic client and just removing the client itself as a show of force (or stupidity) - it would be a real slap in the face.

Again, why is there a need to remove it vs deprecate it, the world will never know.

[klincecum (Kevin Lincecum)]

It is my assumption that Service Connect’s life ends at 2025.2.

[BenWheeldon]

From my understanding service connect can continue to use the .NET references using the power tools client in the same way that DMT does.

However service connect has worked with Kinetic ReST services for a while now.

[Hally (Simon Hall)]

I know way back in 2017 service connect was starting to implement REST…

[Chan213419 (Jeremy Chance)]

Thanks everyone! Indeed, SC has been able to utilize REST for quite some time, but a lot of companies take the position of “if it’s not broke, don’t fix it”. So I see a lot of workflows using the DLLs still. I am wondering if those companies are headed towards a brick wall or not. I guess Epicor is the only one who can answer that. Thank you all for your input on this!

[utaylor (Utah Taylor)]

I think the writing is on that “brick wall”

[Mark_Wonsil]

@Chan213419

“if it’s not broke, don’t fix it”

But it’s going to be broke… Between the classic sunset and Automation Studio…

[Mark_Wonsil]

@Chan213419

re headed towards a brick wall or not. I guess Epicor is the only one who can answer that.

Kinda did over three years ago:

Does Epicor Cloud Support Service Connect

As others have said, you should not do any new development using Service Connect, even if you are staying on-Prem… Service connect is NOT End-Of-Lived YET, but we have removed it from the price list, and we will no longer sell it to new accounts. No new development will be done with it. Service Connect IS compatible with cloud accounts as long as you use REST calls. You cannot run Service Connect on the Cloud instance. You must install it onto another server (on-prem, or your own cloud server).…

[Chan213419 (Jeremy Chance)]

I have seen many environments on the latest version of Kinetic still using .NET refs from the client install (hybrid style that Tim mentioned). I guess the answer is, you can continue to use the .NET refs as long as Epicor allows client installs ya?

[Chad_Smith]

I believe all the DLLs are included in the Power Tools. I think that supports DMT, Functions, APR, and Service Connect as I recall.

[Mark_Wonsil]

I agree with @Chad_Smith. The DLLs are updated with every patch, which is a process that SC users are already used to. Converting to REST will reduce that work unless there’s a signature change. You might even be able to use a Function with REST to reduce the risk further. However, as @timshuwy mentions, you may not want to build your wooden house in a dry forest. Ya never know when a dumpster fire might break out…

[timshuwy (Tim Shoemaker)]

@Chan213419

long as Epicor allows client installs ya?

This is one of the reasons why powertools exists… it is “required” if you also need to do your special stuff with service connect. it would just be better if you used direct calls to the APIs instead of relying on this long term. Example, Automation Studio does NOT need the powertools installed to run because it uses the APIs.

[Hally (Simon Hall)]

Automation Studio is also more of a subscription model too rather than Just paying your maintenance for SC, so there are arguments on both sides.