I have two different schedules for running MRP. 6 days a week, it’s a net change and on Sunday, a regenerative one is run. That’s how it is scheduled and that is how it has run until two weeks ago. Now the one scheduled to run 6 days a week has decided it will run 7.
Last night it kept my regen one from running as that one errored because this one had already started. Workaround is I just moved the other one up 15 minutes so it will already be running when this one starts again next Sunday. Any ideas why this would be occurring? I have not changed anything with either of these scheduled tasks in months so not really certain why this started or even what could be causing it.
This has come up here before. Against any sane logic, it reads the date as local and the time as UTC (GMT/Zulu/London/etc.) and you get some really wacky results.
Upgrading to Kinetic is on our timeline with a goal within the next 6 months. While I am excited for fixes such as this, I do still have a good deal of trepidation and dread for the upgrade with the potential for things breaking that are currently working and having to learn new ways to do things.
If you keep the classic UI you probably won’t have to learn much new function wise.
A lot will break customization wise because you’re really far behind if your posted version is accurate.
In reality it pales in comparison, but in terms of difficulty to transition I would equate 10.1 to 10.2 going from latest 8 to 9.05 and 10.2 to 2022 to going from 9 to 10
We are going from 10.2.600 to 2022.2 when it comes out. My upgrade process to 2022.1 (I doubt anything will break between the two) only 5 things critically broke, and it’s because of .NET6 transition more than Epicor’s changes.
Unfortunately, my posted version is accurate so I’m anticipating the majority of my time in the upgrade will be spent fixing things (we use literally hundreds of customizations). Probably will also find many of these customizations won’t be necessary as Epicor has probably implemented many of the things we do via customizations into standard features in the YEARS since our version was current.
We’re going from 10.1.600, and like Josh said, if you keep the classic client just to get current, most of it does upgrade pretty well. Then we can upgrade items over time as the Kinetic UI matures.
I just did a cleanup of our menu customizations (kept old versions in case of whatever… ) over time… got rid of over 300… so we are left with only 275 to test!
Our goal is similar to Mark, as we will upgrade, then take the time to analyse if we really need all of them, as you mentionned some changes were introduced by Epicor and thus ours are obsolete to maintain…
A huge endeavor for me … As I am now part of a team of one… ;( ( now all alone…we lost 2 in the past year… ).
I’m with you on the team of one side of things so it will be a huge endeavor for me as well and while I am dreading it, I am also looking forward to it. I’m excited to see the improvements and finally be able to ditch some of the work arounds I’ve had to put in place when I research an issue and come across the response that it is fixed in a later version. I’m also looking forward to what I can do with new tools that are available (I’m looking at you, functions) and working with a system that is from this decade.
