Update from 10.1.400.23 to 10.1.600 or 10.2.200?

I know this is a loaded question…

But should I jump “all the way” from 10.1.400.23 to

We’re usually in the “if it ain’t broke” camp when it comes to doing updates. But we’d like to try and keep more current, than we have in the past.

We don’t have any outstanding issues that are resolved in any of the newer updates, and I’ve seen quite a few issues with updating to 10.2.200.

Any advice on going to 10.2.200 (especially any under documented hurdles)?

Should we just go to 10.1.600.30, and wait for some of the growing pains in 10.2.200 to be resolved?

Thanks in advance.

EDIT: … just saw:

Epicor have a really good tool, which will interrogate your database on provide a report on what will be upgraded cleanly and what may need some additional work. This is quite cheap to do , and you can even host in the cloud for a month or two to play with your data in the new format to see how the upgrade went.

1 Like

When he update patches (probably the wrong term for the last segment of the version, like: 10.1.400.23), we just apply them to the test environment, do some testing, then repeat to the Production environment.

Do these minor updates (10.1.400.xx to 10.1.500.xx) require any changes that would prohibit updating just the test environment - since it is running on the same App Server as the Production DB?

And what about major updates (10.1.xxx.xx to 10.2.xxx.xx) ?

How we refer to the versioning numbers we put out there for ERP.

Version e.g. 9.05, 10.0, 10.1, 10.2

Release e.g 10.0.700, 10.1.400, 10.2.200, 9.05.700

Point update e.g. 10.1.400.22,, 10.2.300.2

To answer your question directly: no, you can just update the test environment. Though, releases are not minor updates. We change the database schema and can introduce breaking changes to UI and server-side customization components. That being said, I would never personally put anything on a production server that isn’t production ready and would install anything I was testing on a non-production server.

I would recommend removing the existing appserver at the previous release (from the EAC, IIS, and the Windows file system), and redeploy the appserver with the same name at the new release. Beyond that, from a deployment standpoint, that is all you would need to do in your testing environment. I know the documentation says that one can upgrade an appserver process from one release to another, but, save yourself some potential tribulation and start over with that appserver process.

If the update is more than just a point update, you need to treat the update as “major” with a full testing protocol of quote to cash and of any modifications made (custom reports, BPMs, UI customizations, quick searches, etc).



So to go from 10.1.400.23 to 10.1.600.30, we need to actually “Install” 10.1.600.1, and then update that to 10.1.600.30?

In other words the “update” files on EpicWeb that begin with UD (like UD10.1.600.30.zip) are only good to get an exist installtion of 10.1.600.xx up to 10.1.600.30.

And to “update” from 10.1.xxx (prior to .600) to, requires the RL files like RL10.2.200.zip

That correct?

You would install 10.1.600.0 (base release) and then the latest point update for that release (10.1.600.30). Then, you can upgrade your 10.1.400.23 database directly to 10.1.600.30 in the Epicor Administration Console (EAC).




We went from 10.1.400.28 to 10.2.200.XX It was straight forward. I would recommend it to everyone…

Screen customized needed to be “re-painted”.

I would say about 10% of our customizations needed to be lightly reviewed. 20 out of 200 in total. The rest continued to work without issues.

ARForm report changed that needed a bit of rework as well.

Use the Analyzer it is an awesome tool to document your changes from base.

I’m embarrassed to ask… But what is the analyzer? And where do I get it?

Ask your CAM. It is a tool that @AndyGHA was mentioning . It is free, your CAM needs to set you up with an account. Once you run it, you go online and see some great reports. It is called Epicor ERP Analyser

Thanks. And you had me at “it’s free” :slight_smile:

Does it have an official name?

Epcior ERP Analyzer. your CAM will know. You will get an email from the EPICOR Cloud Upgrade Services, don’t worry there is no charge for the scan.

The report is awesome, as it reviews everything.

Like @knash, we are right now in the testing phase of a 10.1.500.17 to 10.2.200.x upgrade (forget but it might be .7). Same issues with the few customized GUI screens, but it seems that all of our other stuff works just fine, including the configurators (much to our surprise!)