What is this new upgrade for LIVE it 2025.2.14? all about?

klincecum · March 5, 2026, 4:27pm

Make a new thread, show us the code, we’ll fix it in a couple minutes.

Randy · March 5, 2026, 5:09pm

@Epic_Santiago published some GIT docs

gist.github.com

https://gist.github.com/Epic-Santiago/b842d06370cb56d2b1af43ae1f45f5e8

Paths.cs

// Before
var oldPath = @"C:\MyFolder\Test.txt";

System.IO.Directory.CreateDirectory(oldPath);
System.IO.Directory.Delete(oldPath);
System.IO.Directory.Delete(oldPath, recursive: true);
System.IO.Directory.Exists(oldPath);
System.IO.Directory.GetDirectories(oldPath);
System.IO.Directory.GetDirectories(oldPath, "*abc*");
System.IO.Directory.GetDirectories(oldPath, "*abc*", System.IO.SearchOption.AllDirectories);

This file has been truncated. show original

gist.github.com

https://gist.github.com/Epic-Santiago/41b8604ac935ed3ed20461534d6dfd6b

XPlatform.cs

// Replace arbitrary paths like these:
var path = @"C:\Arbitrary\Example.txt";
System.IO.File.AppendAllText(path, "My text");

// With the Sandbox class:
var filePath = new FilePath(ServerFolder.UserData, "Example.txt");
Sandbox.IO.File.AppendAllText(filePath, "My text");

// File name are case sensitive on Linux:
System.IO.File.ReadAllText("myfilename.txt");   // This.

This file has been truncated. show original

kananga · March 5, 2026, 7:49pm

And the desktop client is failing to update. Good thing we punted all of our users into the browser client already!

/edit - I needed to do a thing and because it’s pilot I YOLO’d and manually edited the version number in configs to 12.1.100.14 because what could possibly go wrong. The Pilot desktop client launched successfully enough to realize it could update, tried to update, and borked itself.

JMPCONJ · March 5, 2026, 9:00pm

gotta try to lighten the mood…too depressing

Schae235 · March 6, 2026, 2:37am

In my support ticket I placed to try and understand what is going on they said my environment wasn’t updated because I have self-applied updates selected.

I would expect based on their upgrade policy it still would have upgraded. Can someone confirm an environment that wasn’t upgrade for them was selected as self-applied?

tonyb1986 · March 6, 2026, 11:27am

I feel for you…..we have never had a smooth upgrade - we are 5 years in, i have only been developing for the last 18 months to 2 years now and honestly i dread the updates!

utaylor · March 6, 2026, 2:22pm

What I don’t understand is that the original question to this thread I thought was, are we being upgraded to 2025.2.14 on March 7? Is that right?

What was the actual answer to this question? Yes it’s happening? or was that a mistake?

Just received another email saying it’s scheduled to happen tomorrow:

JMPCONJ · March 6, 2026, 2:37pm

I could be wrong but I thought 3/7 was the flex-1 weekend and 3/20 was flex-2.

JillMetalworks · March 6, 2026, 2:41pm

We are not getting any clear information about the LIVE upgrade. I know it is supposed to get LIVE ready for the Linux transition but I don’t know what else they are throwing into the upgrade. Would be nice if they actually sent details.

It is hard for us to test for the LIVE upgrade as we have turned our Pilot into the Kinetic Web version so it does not match our LIVE version. Epicor is really making it difficult for us to get ready for the Sunset of Classic in June.

I am really worried about Sunday!!!

JMPCONJ · March 6, 2026, 2:44pm

According to an email I got from our consulting partner:

Pilot Update to 2025.2.14 – 3/4/2026 (was done on schedule)
Production Update to 2025.2.14 – 3/20/2026
Pilot Linux Migration – 3/24/2026
Production Migration to Linux – 4/11/2026 or 4/25/2026 as it will be done in 2 phases.

We’re falling in as a flex-2 this round…who knows what the future will bring.

Randy · March 6, 2026, 2:45pm

Pretty sure if you pick self apply you have to do it yourself. At least that how I read the notes.

Randy · March 6, 2026, 2:48pm

From Tim’s post I took it the mistake was announcing Prod update before Pilot but the dates were correct.

klincecum · March 6, 2026, 3:32pm

That would be fine… if the hotfix was available in the list…

klincecum · March 6, 2026, 3:33pm

Spoke too soon lol

Taylor_L · March 6, 2026, 3:34pm

Looks like our configurators are taking forever to do anything now. There are multiple pages in our configurator and each of them take multiple minutes to load or just dont load at all. The debug log shows hundreds of iterations for each field on the page. In the live environment it is perfectly fine, 0 iterations for each field. Did you make an epicor support ticket for this?

EDIT: Just made a ticket for this and I was told development is looking into this now. Hopefully this is the only issue with configurators in linux because we just can’t test at this rate.

blapp · March 6, 2026, 4:13pm

I submitted a case for the issue. The Problem #PRB0313744.

It looks like it will be an issue in Production on Monday according to this response from support:

I actually can duplicate the issue in my demo database which is on Windows. I never noticed an issue because I am usually only testing smaller configurators but it looks like it eventually gets hung up on inputs.

I am pushing to get more information on this and I will keep you updated.

I am trying to figure out how we can manipulate it, so it doesn’t iterate through all the fields.

blapp · March 6, 2026, 4:16pm

Maybe @timshuwy can get a hotfix added to the update for us this weekend or add us to one of the Flex options for this time…

Taylor_L · March 6, 2026, 4:21pm

Are all the configurator fields on one panel? I was told that making separate panels for each section and then putting them in a stack panel makes the loading a lot faster. That really helped us. Each configurator field only iterates when it is opened for the first time. Like I said usually it is 0 but now it is 384 now.

utaylor · March 6, 2026, 4:31pm

So it is or isn’t happening?

Randy · March 6, 2026, 4:39pm

I got another notification email that it IS so

Im Fine All Good GIF by Pudgy Memez