Patching - suggestions/experience

Question

We just come on the situation, when the client asks for the latest patch on his Sage v12. 
 Our administrators are afraid to patch Sage, as it could lead to unexpected errors/problems with system stability and/or existing developments in Sage. 
 It is understandable - that latest patch is recommended. 
 What is your experience/suggestion regarding patching?

Rafael · Accepted Answer

Kevin, 
 There will be slightly different processes depending on if it's a single tenant or multi-tenant cloud solution. It depends also on if you're using Sage's internal AWS hosting or it's done through Net@work X3 cloud hosting. Generally speaking, Sage will patch up the multi-tenant environments with plenty of notice ahead of schedule. I don't think that the patching only to a Sandbox environment process is in place yet. I know that Netsuite follows this process, patching in a Sandbox several months prior to the actual live upgrade in the Production folder. 
 If you have single tenant you will have more flexibility on SPE mods, but there are still limitations.

Julien Patureau · Answer

The way you customize Sage X3 can have more or less impact on the patching process. 2 examples: 1/ If you want to hide a field: modifiying the related screen in the screen dictionnary will have an important impact (lower if only the field hidden is protected with an activity code and not the entire screen) but using the 'Customize page' feature will have very low impact (if not at all). 2/ If you want to add your own custom fields on the product record: you can add them in the table ITMMASTER and in the existing ITMx screens. This will make both the table and screen difficult to patch. But if you create your own customer table (ZITMMASTER) with the same index and your own screen (yet linked to the OITM window) you have almost the same result but without having to use activity code on he table ITMMASTER and in the existing ITMx screens. Of course in some cases, you have no choice but to modify the standard elements but the less activity codes you have the less error you will get when patching. Upgrade is a general recommendation, but at the end you have to respect the business constraints. If you have not much employee then maybe Sage X3 cloud or hosting can be a better option (not available yet in all geographies). To take the same example you did: this is like paying an insurance on the wheels of your Ferrari. I hope this helps.

Sage X3

Patching - suggestions/experience

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING