Just wanted to report that I did my first over writing of Pilot with a copy of LIVE in the Cloud Management Portal and it was a success!! Took about 45 minutes to an hour. You have to keep hitting the Refresh button to see where the process was at but it does work. So happy all things went well. Happy not having to rely on Tech Support to do this anymore:>)
No, it seems all the necessary steps are already built into the CMP scripts. I have done this multiple times and have not hit any âgotchasâ related to the refresh process.
The biggest one is that the environments must be on the same version. If they upgrade PILOT to a new version, you canât copy LIVE to PILOT.
For example, there is a scheduled âHotfixâ for non-production environments scheduled for this Wednesday 10/01/2025, and Production on 10/04/2025. If you try to copy live to Pilot before the hotfix goes live on Production, it will error out.
The only gotcha is you have to every so often hit the big âRefreshâ button on the screen to see what the progress is. You donât need to do anything to your database ahead of time. When it was done, I did my normal things after Epicor had updated my Pilot database with a copy of LIVE and moved on with my day. Easey-peasey!! Easier than I thought it would be.
Thank you all for the positive feedback. I forwarded these comments to the dev team (and their leadership) that is responsible and I received back comments such as âGreat - thanks for sharingâ, âNice, I love seeing thisâ, and âThereâs nothign better than hearing from another customer about their experience.
This feature has been a long time in coming. it was critical that we get it right, and there are a lot of moving pieces. Please keep the feedback coming. Also, use Epicor Ideas if you have improvements that you see could be made. The Product Manager over this area does monitor and respond to new ideas.
I am still too scared to use the feature as Epicor passed off all responsibility to the end user if something goes sideways. I canât take that risk. Give me a solution that doesnât allow me to mess anything up. The last I read about this feature, if anything goes wrong during the overwrite, Epicor is not responsible and will probably charge you support to fix it.
I really want to use this feature, but not with those risks. Iâll keep submitting support tickets to keep the risk on Epicorâs side.
I seem to recall this was true for major version mismatch. Is it in fact true for hotfix as well? Do we know if minor version a CMP limitation or a hard incompatability?
We just so happen to wanna refresh tomorrow, bummer.
Is this the current status? I donât seeâpreviewâ labels or any such warnings in the CMP release notes or help articles. Did I sign something on this? One would think support wouldâve been using it for QA before release.
I also have had good success using the refresh function. Not so much the update function. Out of 4 non-prod environments, 0 updated successfully on their own. Had to go through all the trouble of doing the update in the CMP. Then enter support cases and wait for cloud ops to fix it anyway. So really just major extra work, hassle, and downtime at this point for dot releases which cloud ops ought to be doing for us anyway.
We have a âfourthâ environment that I always reload from Live right before any update. It gets updated at the same time as Pilot, so I can always restore Pilot or Test from âFourthâ. Itâs a good workaround. I think the hotfix isnât until tomorrow, so if you want to restore now you probably can.
Once you approve the T&C you canât see them easily again. Maybe someone that has not approved for the first time yet will show us the T&C that we all blindly agreed to.
Weâre new, still trying to implement. Only refreshed twice before and thisâll be the 3rd time caught in the gap. Probably should put a hold on updates but weâre waiting for a few PRBs. My notice says we have til 7pm tonight else next Monday.
Off to solution tracker to sort things out. Wish me luck. Go Cloud!