You can even cross the streams… Emacs in the Browser Using Codespaces
We are about 50% browser users so far and they’ve all said they will never go back to the smart client. That said, I’m a little worried about the switch from the classic configurator to the Kinetic one as there seems to be a few bugs in there.
It’s not ready in 2024.1 either, especially for Data Directives. I find it much simpler and less of a headache still to login to our server, into the smart client, and work on BPMs (method or data) in the Classic version than the browser.
Welcome @JasonB !!
The CFG is still a royal PITA. It’s going to take some re-thinking. But I will say that it’s getting better. We stopped working on it to wait for the editors (the last thing Epicor was working on in the timeline) and will give it a proper go in 25.1.
We live and die on the CFG and can’t take any chances with it.
I’ve still been holding off as well but it feels like playing chicken. I’m 78% convinced it might be better just to do everything in Epicor Functions and Appplication studio. Seems like configurators get minimum attention.
I asked some very pointed questions and I’m told that the CFG is not going away, and that 25.1 should provide the final missing/dysfunctional tools we need to migrate. My fingers are crossed!
Tim, will the command line BAQ export/DMT processes still work? We have quite a few power shell scripts that do this sort of thing. Naturally the server on which they run would need to have the power tools installed. We are on-prem.
Thanks - Carol
Great Question… (Something I actually dont know). @Pat_F do you have an answer for this? will you still have a command line ability to run a BAQ Export?
can you show how your ps script looks like?
Hi Tim - wish I could help but you have the wrong Pat!
@timshuwy, I think you are looking for @pferrington
Maybe your responsibilities have been expanded.
Hi Olga. Thanks for taking a look at this. Here’s the meat of the powershell script.
Start-Process -Wait -FilePath $DMTPath -ArgumentList “-User $User -Pass $Pass -Export -BAQ GetPartsForUD32 -Target $Source -NoUI ConfigValue=Epicor10”
Start-Process -Wait -FilePath $DMTPath -ArgumentList "-User $User -Pass $Pass -Update -Import UD32 -Source $Source "
Sounds like Functions will start as a power tool with a preview browser version in 2026.1. The power tool version will be removed after 1 year.
I’m good with this as long as the new editor works the same if not better than the current one.
Agreed.
I can’t see why they don’t have a common editor for BAQ, BPM, and Functions. It could be so much better than having separate ones that aren’t as good as even Classic’s were.
I vote just to leave the client there with a big asterisk that says NO UPDATES. I get it, how you can force people to do something they dont want to if they have an option.