Sure would be great if they posted release notes ahead of time. As of this post, nothing for 2025.2.14 just a few days before they install it on Cloud environments:
However, release notes (from .7 to .10) didn’t exactly tell us they were going to systematically break how we applied customization layer to nearly all of our Menu ID’s and put us in a scramble to fix. Thanks Epicor for that one.
Not to pile on here, but it seems these inaccurate emails are sent too often. They are anxiety inducing to say the least. Seems like something that’s easy to fix.
As someone else posted recently, your customer’s --especially SaaS-- have so much anxiety from multiple episodes of botched communications, buggy updates, and outages we practically need therapy. We’re here yet again with this instance.
When is the .14 notes releasing? With only a few days between PILOT and PROD getting .14 and without enough advanced notice to plan a full UAT. It’d be nice to review the release notes before PILOT gets the update to plan focused testing.
I requested to have our Pilot environment updated to 2025.2.14 tonight, so we have a few extra days for testing. This is the response I received from support:
unfortunately, we can’t schedule this for your preferred time window, as this update will be available after it will be deployed globally, it should be around Thursday.
It appears like version .14 will not be available until after they make a change to the backend…?
We used to get more time to test dot-patches in PILOT before they’d roll it to PROD.
I don’t know why the sudden acceleration. I was thinking 26.1 requires Linux containers but that doesn’t make sense as on-prem is staying Windows.
I do wish they would also update the EpicWeb. As of now, the 2025.2.14 update is still not on EpicWeb. I know it’s on status.epicor.com but the EpicWeb usually shows a bit further ahead.
No doubt this is the start of version environment separation. Don’t be surprised if the on prem version for 2025.2 ends up have different updates.
There definatley legitimate concerns and based on the list of people posting.
One of the biggest concerns I have not just with the poor communication, is the fact that the only person who was able to clarify was @timshuwy. He has been around for a VERY long time and at some point people retire…
Epicor please implement a human vetting and approval process for communications IMMEDIATELY. These communications should be 100% accurate 100% of the time. This should be one of your SLAs.
the powers in charge of the announcement are currently working on finalizing the information. Due to a few factors, the exact date/time was not yet set in order to make sure we didnt blitz you with a date and then changes to that date. Trying to get it right the first time.
and while I am on my soapbox.
This sort of think is also unacceptable. I know “contact the documentation team” and the typical response is “Why are we doing Epicor’s job for them?” and I’m happy to help, but when it’s the spelling of the product… that’s really going a bit too far.
Pot calling the kettle here a bit I know I’m the first to admit my posts are full of spelling errors and mistakes, and multiple edits. But I’m not a commercial entity selling a brand/product to businesses that for the most part rely on its accuracy to run their business. It reflects very badly.
@moderators, if this is an unacceptable post then please by all means delete.
I am now crawling back into the corner of the room into the foetal position.
haha… still need to pay for my new Kitchen… going to be a while.
Outside before deck was complete, but you can see the new kitchen exterior.
Note that big 5’ x 5’ picture window (as well as two other smaller windows) were purchased from Habitat for Humanity’s “Restore” store for $145… it is probably worth at least 15 times that value. the kitchen wall and cabinets were designed around the window.
Nice pics @timshuwy
I guess what I was trying point out in my post is at some point peoples contributions will stop… for various reasons, not just retirement and there seems to be somewhat of a gap in clear communication to the customer base. For example the customers that don’t use EpiUsers (why you wouldn’t is beyond me)… but there are. How would they know.
Just asking “Please do better” and “Tell us how you are going to prevent this misinformation in the future”
Transparency is the key… At the moment with all the change it seems we are sailing the seas like.
Need some input from experts here.
We have scheduled the Cloud conversion for this weekend many months ago.
We are doing the conversion on the Friday 6th 2026 and it will convert to 2025.2.10.
Epicor will upgrade production to 2025.2.14, the scheduled time is 5pm on Saturday to 9am Sunday the following day.
Then plan to Go Live on Monday 9th 2026 with new version 2025.2.14.
Here is the scale of the customisation we have in place at the moment.
Should I stick to my plan or postpone?
I think I’d postpone. You don’t want to start out on the wrong foot and be down come Monday morning. That won’t build trust with Epicor with any of your users.
That’s a lot to test in a day - over the weekend. If you need support it’s limited over the weekend. There’s also been a lot of issues with recent updates. I wouldn’t bet on everything going well. And I’m not just saying that as to pile on about Epicor SaaS. The release notes aren’t even posted for .14 yet.
Sorry, feeling a little blitzed here with only two days to test in PILOT before going to PRODUCTION.
on 2025.1.11
I have a couple of questions.
going to upgrade LIVE on Friday evening GMT - on Flex 2 but we need to roll early due to end of year in business. If we upgrade on Friday and the 2025.2.14 is deployed on Sat 4pm GMT - will this cause issues?
If i delay the upgrade on Friday will the 2025.2.14 also be delayed? or can we opt out on this .14 upgrade.
Epicor are slow are coming back on answers so if you folks can help or point me to the right place
Also what is contained in this upgrade? that might help answer some questions also.
Do you have the cloud management portal? if so, you could choose to upgrade early on your own schedule. The fixes in the .14 patch has no functionality changes, but it does fix things that make it compatible with the future linux rollout. As you have seen people have had problems with previous patches. We have a team who is attacking each reported unforseen issue as they arrise.
ALSO for everyone… please keep this dialog going with good information. (I feel like i am a broken record saying this): We DO watch this forum. Just yesterday, I took a post and forwarded it.. i was in at least high level meetings where the post was referenced. You are making a difference.
Thank you
The plan was to upgrade via the CMP -
Friday was the day selected until we saw this patch - As it happened we had to roll back Linux patch on THIRD so this makes sense
Thanks for the update
Just a side note that in the vein of @Schae235’s post regarding the update not being available on Pilot/Non-Prod, it would be excellent if the (ERPCurrent) version was available on Education, automatically upgraded by Epicor at the soonest availability of any Upgrade/Update/Hotfix version, without manual intervention.
This environment poses an excellent opportunity for Customers to test out various scenarios, and it is already acknowledged by agreement that this environment hosts only training data, so expectations are not outside the norm that it be nuked during an upgrade/update as schema modification needs dictate.
On an update cadence, this would be great to test modifications in-place immediately first thing in the morning without needing to manually trigger an environment update through CMP and await the subsequent task completion.
Those extra hours of new-logic availability may make a significant difference in cases like this one where we are given appx. 16 hours of working time to analyze impact.
I think it’s pretty clear that the rollout of 25.2.14 could have been better communicated, planned, etc.
One thing I would advocate for in the future is when updates will be available in the Cloud Management Portal for self-applied updates/upgrades.
For instance, the upgrade to 2026.1 I can tell from the 2026.1 page that it is planned to upgrade the pilot instances May 14th through May 16th (For my data center) but I have no idea if I can manually upgrade the pilot instances earlier and if so when.
