Totally makes sense as PILOT is updated a couple of weeks before LIVE. But this is preventing me to immediately move stuff between environments when versions are not the same.
Is there a best practice to managing this? Is there a way to prevent this?
Not sure if helps but we have three environments: LIVE, PILOT, THIRD.
The simplest way to avoid cloud is… Go On Prem :)… Then you are in total control of all of your environments… But then you forgo all the benefits of cloud… I’m sure there are a host of people queuing up to spruke the benefits as they read this…
In the Make the software friendly for DevOps practices, source code would be saved by version but uploaded by capability. What I mean is that the source code is saved in the version in which it is created, but if compatible, could be imported into any version. It’s the import/export/solution system that’s blocking.
In the old days of web programming, we added all kinds of conditional code to handle various browser versions. They eventually gave that up and just tested for the capability and used what it could. I’d like to see that with customizations as well.
Initially, I was optimistic about moving to the cloud after Insights 2024, but I value having control over our environment. Epicor AI just seems like fluff. Seeing how Epicor synchronized multiple users data together and even modifies code within user databases reinforced my preference for on-prem. I’m confident that staying on-prem was the right decision for us.
