Hi,everyone. Our company is a new Epicor customer and is now preparing to install the Kinetic system. However, I’m hesitating between installing Kinetic 2024.1 or 2023.2. The 2023.2 version might be more stable, but the 2024.1 version could offer better performance since it uses .NET SDK 8 and might come with more features. I’m not sure which one to choose; do you have any suggestions?
We haven’t noticed any significant problems with 2024.1
Thank you for your information.It’s helpful.May I know how long have you been with 2024.1?
We are in the process of upgrading from 2022.2 to 2024.1 at the moment. Have been using Epicor on Prem since version 9.05 so about 10 years.
I take it you are installing on prem as well. If you are at the installing Epicor stage then you will be about to conduct a bunch of testing to ensure it works for your business needs. I would recommend you do that testing on the latest version available, this will give you the biggest gap before you need to upgrade it and go through that testing again.
Brett
1 Like
We’re Flex 2, so just our pilot. We’ve just been doing all our testing, and that’s where I do all my development.
As a general rule, 2024.1 is the better option. At the user level, the Kinetic interface has one more versions’ worth of stability fixes, and the product really is maturing before our eyes. There are new features, there are fixes to many screens, several “ideas” created by members of this forum (and others) have been folded in, and as @klincecum mentions, there aren’t any significant problems that didn’t already exist.
With the somewhat more consistent and rapid upgrade cycle, it doesn’t really make sense to start out a version behind UNLESS there is a specific good reason not to. Epicor has a “major” release twice yearly and “service pack” releases every couple of weeks. It is not a good idea to get TOO far behind, and if you start out already behind then everything else comes quicker.
5 Likes
I agree with prior posts on using 2024.1. I’ve not seen any major issues, and the screens and menu searches are much better. Since you are in testing phase, it’s best to do the testing in the latest version so you aren’t behind the curve at go live.
3 Likes
My rule of thumb past few years has been to wait for the 20XX.X.10 ish patch before beginning an upgrade on Prem. I think we are right around there for 2024.1 already.
I tend to feel more comfortable with the 20XX.2s than the 20XX.1s, but as others have said I think 2024.1 is the right move for you.
What’s your timeline though? If this is a year + new implementation you might start on 2024.1 but end up on something like 2025.1 before you go live.
My pilot got 2024.1.10 last night.
1 Like
Another upvote for 2024.1 is that multiple issues our users encountered were fixed in the new version.
@klincecum did you have any issues launching your Pilot environment after the 2024.1.10 upgrade last night? Are you using smart client or web browser? We cannot launch smart client after the update nor can we download a new install file as that errors. I can log in via the web browser but we do not use the browser yet.
My thumbs up to go to 2024.1 also. The product is maturing with every major release, feeling less and less beta.
1 Like
Not this time, but I did with the upgrade to 2024.1.8.
Luckily, I was able to download the correct client from https://download.epicorsaas.com/
Thank you very much,your information are very helpful.We are about to formally kick start the Project next week.We are trying to migrate our business from another native Chinese ERP software to Epicor Kinetic.It might take 6 months or more before everything is done.So it more likely start on 2024.1 and end up on 2024.2 ,as you said,20XX.2 might be more comfortable.
1 Like
Vote 1 2024.1
1 Like
2024.1.10 had a bit of a hiccup in our pilot environment, every module was just opening to a grey screen, but epicor support eventually fixed it. Other than that, I do mostly like 2024.1.x. Getting rid of the landing pages is great.
1 Like
Yeah, this is always a tough judgement call. There will come a point in the implementation where you need to lock in what version you’re going Live on. In my opinion by the time folks are validating end user procedures or when any custom development is being programmed you should try to be locked in.
The first few months are often about learning the system, process mapping, architecture, etc., and it’s less important to be sandboxing in the exact version you’re going Live on.
Although, if you upgrade mid-implementation that is time and energy you have to budget for. If your company is trying to be aggressive as possible on the timeline, this might not be the right move. Otherwise I like your thinking of starting on 2024.1 and landing on 2024.2.
1 Like
Thank you all guys.All comments are very helpful.I’ve decided to start on 2024.1.As you said,it’s most likely the better one.