My pilot is on 2025.2.10…
Are they going to upgrade us to .14 first?
Anyone know?
4 Likes
We already got bumped to 2025.2.14 in Pilot…but went live on 2025.2.10 this weekend. Seems odd but whatever.
1 Like
Mine is still
Well, that’s what you get for being flex… 
2 Likes
4 Likes
My PILOT is on 2025.2.14 and also on Linux.
ALL of my EDI paths were updated to the new linux path. I did not do this. I am still waiting for clarification from support if the update changed it, or if support changed them, but I certainly did not.
If the update changes them, I wonder how that interacts with the environment still being on Windows if the 2025.2.14 update comes first, or vice versa.
2 Likes
Checked our Pilot…tried manually running the Import EDI Demand with the Windows location, failed as intended, then used \epi\fs and reversed all the slashes and it ran fine. Will have to see how the rest of things go with printers and other EDI tasks. Good thing we don’t have an urgent need to test much in Pilot after last weekend. 
EDIT - our EDI stuff didn’t update properly in Pilot…again…LOL
Some functions still show the traditional Windows path…and I found THESE beauties…
/usr/local/app/\######.file.core.windows.net######\Pilot\EDI\IN\852/852.log
/usr/local/app/\######.file.core.windows.net######\Pilot\EDI\IN\867/867.log
1 Like
PILOT is upgrading to 2025.2.16 on 3/31, with PROD following on 4/11.
So PILOT went .10 → .14 → .16
And LIVE is going .10 → .16 ??
We weren’t meant to test .14 in PILOT right? or were we meant to test .14 and not test .16?
2 Likes
Yeah that seemed odd to me too…went live on 2025.2.10 this weekend…why were we forced to 2025.2.14 in Pilot and then not made live on it?
2 Likes
Because .14 update in live was pulled at the last minute due to what I understood be configurator loading performance issues which they did not want to plague people with in live.
It was then Rearranged to .16 to include fixes for it. However pilot was already upgraded and cannot be downgraded.
I did realise the other day though that CMP refreshes can work across patch versions.
1 Like
Aha…that explains it well…thanks.
If the update changes them, I wonder how that interacts with the environment still being on Windows if the 2025.2.14 update comes first, or vice versa.
Paths are only updated when the OS is Linux.
2 Likes
EDIT - our EDI stuff didn’t update properly in Pilot
What version are you running? Most known Linux issues are fixed at 2025.2.15. Unless you have upgraded to that version yourself from CMP or support did it for you then you are probably on 2025.2.14.
2 Likes
For live, if the update comes before the linux switch:
My paths will not update, and then when live is moved to linux, stuff breaks and I have to update them?
If Linux comes first:
My paths will no longer work, stuff breaks and I have to update them. Then the update comes and hopefully I don’t notice?
I am trying to get some clarification about how ready I need to be for the changes coming to live.
If you can, give .15 a try. If you still have path issues we can investigate.
And this goes for everyone and all Linux issues. Most known issues have been fixed in .15 so if you are experiencing any issues you suspect are Linux related, consider updating to the latest available version on CMP. I think we’re at 2025.2.15-b at the moment.
1 Like
The updates run on AppServer startup. When your AppServer starts, if it is on Linux it will update the paths. If it’s on Windows, it will do nothing.
This is for absolute paths that are stored in the database.
But as I responded elsewhere, you want to be on .15 to get the latest conversion available.
2 Likes
Sorry but I am still confused.
In either situation won’t I have to update my paths manually?
If linux comes first I assume my existing windows paths will stop working.
If the update comes first my paths will stay windows paths and will continue to work until live is on linux, at which point they will stop working.
I must be missing something.