Handling the rollouts better and minimizing the seemingly-more-frequent maintenance windows would go a long way in easing the anxiety levels. Every couple of days we’re getting popped for something lately.
4 Likes
I have always wondered this myself. EpicCare had told me previously these are only released after the upgrade. Seems backwards to me as I would love to know what is changing and so I know what I am walking into Monday morning.
3 Likes
It is very difficult to upgrade early when its not even available in the CMP until today 3/4 AND you aren’t even allowed to upgrade because you are within the 48 hour window of when the cloud team forces it.. for self managed instances. I tried:
Here is their Policy incase you weren’t aware:
8 Likes
My regen is failing and I’m not even set to be upgraded. I’m flex 2.
2 Likes
From talking with support it’s expected that CMP doesn’t let you do stuff during any worldwide maintenance window, we are Flex 2 as well and have encountered the issue multiple times.
3 Likes
At this point I don’t know what our Pilot’s going to be at tomorrow. We were/are on cadence, we flexed initially because we’d just moved to the cloud, we got lumped into flex-2 for 3/20 after the Linux Pilot disaster and restoration.
2 Likes
Good luck!
2 Likes
More like
5 Likes
After some initial testing it looks like the azure path issue is fixed.
7 Likes
I can confirm that our custom label program printed successfully with our standard windows file paths after testing this morning. A nice plus.
2 Likes
Beautiful.
We are experiencing major issues with our configurator since the update last night.
We are now seeing these calls being made for every column that is on the configurator screen:
This is not good. It takes a long time to configure one part.
5 Likes
Pilot at 2025.2.14 this morning. Flex2 go-live is weekend of 3/20. 15 days.
Should be fun.
1 Like
We’re on cadence and I checked CMP this morning after not getting a single maintenance email and we’re on 25.2.12 still. 
We’re also on cadence. We had updated our Pilot to 2025.2.12 on Monday of this week but had left our Third at 2025.2.10.
This morning our Third was updated to .14 but Pilot is still on .12.
I have to wait to update Pilot until Epicor has completed the update for all US regions.
I thought Epicor automatically updates to the latest version if we don’t do it before the scheduled update. Didn’t happen this time.
Our Pilot was updated. We do not have a 3rd. I didn’t do anything manually, I did submit a ticket to EpiCare for the Azure path issue. Odd that some environments were updated and some weren’t.
Our bartender file path is defaulting to the linux file share for the label templates which is not mapped on our file server. The azure is though. Epicor support just told me to look at this for information but I couldnt find anything about the file share.
Epicor Kinetic
Here is the raw code for the output file in a BPM:
fileName = Sandbox.Compatibility.ConvertPath(btPath + @"\CartonLabel_" + DateTime.Now.ToString("yyyyMMddHHmmssffff")) + @".bt";
sOut = @"%BTW% /AF=""" + Sandbox.Compatibility.ConvertPath(btwPath + @"\" + sTmpl) + @""" /D=""<Trigger File Name>"" /PRN=""" + sPrinter + @""" /DBTEXTHEADER=3 /R=3 /P" + Environment.NewLine;
sOut += @"%END%" + Environment.NewLine;
sOut += "PackNum^SupplierNum^PONum^OrderNum^JobNum^PartNum^PartRev^PartDesc^Qty^NetWt^GrossWt^LabelType^PkgType^" +
"LicensePlate^Trigger^Dest^Station^NumCartons^STName^STAddr1^STAddr2^STAddr3^STCity^STState^STZip^STCountry^LabelComment^ShipDate" +
Environment.NewLine;
the btPath variable is a user defined code that points to the azure file share. The result bt file that goes out of the pilot has the following:
%BTW% /AF="\\*****.file.core.windows.net\*****\Bartender\Labels\StdCartonLabel.btw" /D="<Trigger File Name>" /PRN="\\*****\ZD621" /DBTEXTHEADER=3 /R=3 /P
But the pilot bt files have the following:
%BTW% /AF="/epi/fs/Bartender/Labels/StdCartonLabel.btw" /D="<Trigger File Name>" /PRN="\\*****\ZD621" /DBTEXTHEADER=3 /R=3 /P
This probably has something to do with the Sandbox.Compatibility.ConvertPath bit in the file name, but I am not sure if I should change that.
Edit: I removed the sandbox compatibility part and it just shows a bpm error now.
1 Like
I got it. I just had to replace the first sOut with this:
sOut = @"%BTW% /AF=""" + btwPath.TrimEnd('\\') + @"\" + sTmpl + @""" /D=""<Trigger File Name>"" /PRN=""" + sPrinter + @""" /DBTEXTHEADER=3 /R=3 /P" + Environment.NewLine;
If anyone else has this issue I hope this helps them.
1 Like
That code is going to break, as it is obsolete, even though epicor converted it.
Go ahead and use the new Sandbox methods now.
1 Like
Drat. Looks like I have some research to do on sandbox methods and also figure out the best way to do this. Thanks for the warning