General Consultant Discussion

As a rule of thumb I follow the ""if it ain't broke don't fix it"" method of applying product updates for end users. However I recently ran into an issue where a user performed a customer merge in 2013 and they did not have the product update which fixed the issue with bad merges. Luckily we were able to correct it but not without some time and manual labor. This has caused me to reconsider my reluctance to install Sage product updates as simply a precautionary measure. I'm now thinking that it may be a better procedure to install the product updates as they become available since it's impossible to know when a user may suddenly encounter a bug that has been patched in a PU. First question deals with whether you would consider strongly recommending that end users install the latest product updates. Since Sage is now only issuing product updates for 2014 -- that probably also means that you recommend version upgrades so that the user is on a patchable version (let's presume that we won't one-off hunt for individual fixes).

Will contact client if one of the fixes applies or it critical.

Ditto. Usually wait for a reason to install a product update.

Ditto. Review updates and recommend installing on a case-by-case basis.

The updates are just as likely to break something that is a daily essential as patch something that's a once a year problem.

I've had enough experiences with a product update breaking something, that I'm still of the mindset to take it on a case-by-case basis.

And you have to check the compatibility of enhancements before installing updates.

Product Updates are brought current as part of an upgrade to a new version. Otherwise they are install only if they solve a critical current problem.

ditto - if it aint broke don't fix it!

If it isn't broken don't fix it

You people are no fun. What about the excitement? What about the drama?

Well I think we need to update all of our customers to version 2015 initial release starting today since it is available for download!

I think release 2015 will be better than most have been due directly to the active participation of the 90 Minds members in the beta process. I'm still take the 'wait and see' approach with updates and upgrades and do not recommend that a user implement immediately unless there is a compelling reason.

I was at a customer yesterday and mentioned a feature of v2015, ""...which, by the way, is being released today."" His response: ""Did you bring it with you?

I install if resolving a critical issue or due to payroll / aatrix requirements Otherwise will install the current service pack when I upgrade.

I do mine on a case by case basis. I am challenged enough just trying to get client's to upgrade!

I'm pushing 2015 mostly for the payroll customers (ACA reporting). While some of the doc said that the ACA mods would be available as far back as 4.50, the person showing the enhancements in the 2015 webinar said 2014 and 2015 only, so until I SEE those enhancements, I'm going to guess they decided it was too much work.

Can't see ACA for v4.5 since that version will be retired this fall.