10.2.400.14 vs. 10.2.400.17 (current 400.13)?

[nhutchins (Norman Hutchins)]

Good Morning Fellow EpiUsers,

A quick question we are currently on 10.2.400.13 and need to install a point release to correct the job costing issue sooner than later. Support says it’s fixed in 400.14. However, 400.17 is now the current release. The question is, do I do what’s required (14), or do I jump to the current level (17)?

A few more details;

• don’t have time for complete thorough testing as I would normally do
• year-end physical inventory starts next week (26th)
• I leave for vacation on January 4th

Does anyone have any thoughts or know of any issues with either .14 or .17, that I should be aware of? Things I should definitely test before upgrading?

[utaylor (Utah Taylor)]

What was the costing issue? We just updated to 10.2.400.9… so I am of no help for .17.

[nhutchins (Norman Hutchins)]

Incorrect MFG-VAR transactions since upgrading to 10.2.400.13

Interestingly, I received the following email from Epicor this evening. Dear Customer, This is a notification that a costing issue reported within the Core Application, If you use backflushing within job costing and are on an earlier version of 10.2 than the versions listed below, please contact support to receive an expedited fix: 10.2.200.34 GA 11/31/19 10.2.400.14 GA 10/25/19 10.2.500.3 GA 10/23/19 You are receiving this notification because our records indicate you are on a prior ver…

[utaylor (Utah Taylor)]

Ah yes, I remember reading this a few days ago.

[Alphanu (Ben)]

Hi Norman,

We are currently on 10.2.400.14 in our live environment, there are currently 2 issues that effect us which are:

1. Epicor Looses focus when loading subforms. Any other desktop application then gains focus.
2. BPM DataForms no longer work on dashboards loaded from MES.

We did have a couple of other issues with reports but these were easy to fix.

We have upgraded our test environment to 10.2.400.17 the upgrade was fine, we did not seem to have any new issues. However, the issues mentioned above are still there. Epicor support have informed me that these issues will be fixed in 10.2.400.18. This is due for release on the 20th.

Every Epicor environment is different, I would never recommend upgrading without testing. Even if someone tells you they had no problems with an upgrade, this does not mean you wont.

[hkeric.wci (Haso Keric)]

You can upgrade to .17 directly, it shouldnt take much.

In a Nutshell give or take:

1. Install Update
2. Switch your version on Admin Console
3. Epicor will Upgrade
4. Run Epicor, it will run Conversion Workbench
5. In a Nutshell you are good to go - Update all your Clients, or they will just run Auto-Update which is fine too.

[nhutchins (Norman Hutchins)]

Thanks @hkeric.wci, I was aware that I could jump to .17 and of the upgrade process. I was more asking if anyone knew of any current issues with .17.

[markdamen]

I’ve not been burnt with applying that level of upgrade - if you’re going to .14, go straight for .17.

Epicor are committing to not delivering any breaking changes within that level of update, so should be all good

[chaddb (Chadd Blanchard)]

We went from 10.2.400.14 to 10.2.400.17 this weekend. No major issues we’ve noticed in .17. I would skip .14 and go to .17 or wait for .18. It sounds like .18 is ready for release this week.