Please make sure that all fixes provided in Product Updates are well documented in the knowledge base. This is important because some of the problems that have been fixed could be issues that were introduced in a version that is newer than someone’s current version. By upgrading to a PU that is say, one version older than the current one, these known issues would be introduced into their system as new problems.

Often times people cannot upgrade to the most recent Sage 500 PU because they are using 3rd-party add-ons and therefore must wait for the publisher to provide a compatible version. By the time the updated add-on becomes available and the administrator completes pilot testing, a newer PU will have been released by Sage. The bugs fixed in this most recent PU will of course exist in a system that is upgraded to the second most recent PU, which is often the latest PU that folks can upgrade to. We use a 3rd-party add-on, therefore we can never upgrade to the most recent Sage 500 PU. The best that we can ever do is the second most recent PU.

Sage 500 admins need details about these resolved issues so that they can evaluate them prior to upgrading in order to determine if any of them are showstoppers.

Comments

  • Agreed... there needs to be an easier way to see solutions that have already been addressed rather than opening a new ticket to something to later find it has already been fixed