Schulz Consulting

Sage 100cloud Consulting

Sage 100 Version Cross Reference: Year to Number

by

 

Have you looked at the Help – About screen within Sage 100 or Sage 100c and wondered how the numeric version displayed relates to the Sage 100 release shown on the program splash screen?

For example, Sage refers to Sage 100 2017 internally as 5.40, Sage 100 2016 as 5.30, etc. If you open the program and look at the Help – About menu you’ll see the version is displayed only as 5.40 or 5.30 respectively. Yet, in this example, when you initially start Sage 100 the version displayed on the program splash screen will be 2017 or 2016.

There’s now a quick reference guide to show how the common version number (ie 2017) relates to Sage’s internal number (ie 5.40).

Splash Screen Version Sage Internal Version Released Payroll Version Download Product Updates Through
2018 6.00 October 2017 2.17 TBD TBD
2017 5.40 October 2016 N/A 2017 6/18
2016 5.30 November 2015 N/A 2016 6/17
2015 5.20 April 2015 N/A 2015 6/16
2014 5.10 February 2014 N/A 2014 11/15
2013 5.00 December 2012 N/A 2013
N/A 4.50 August 2011 N/A

 

 

 

 

 

 

 

 

 

Sage published a handy chart which references the major release number (the year which is used for marketing purposes) to the internal version number  (the number used for Sage’s technical/internal support).

Beginning with the 2013 release Sage started assigning annual releases a year as the primary version instead of the simple numeric they’d previously used.

This was so users can easily view how current they are with their installed version by relating it to the current year.

Sage 100 and Sage 100c next release is version 2018 (aka 6.00). We expect this to be delivered in the fourth calendar quarter of 2017 to users with a valid maintenance or subscription plan.

It is increasingly important to stay current annually with new releases.  Once a new release is issued prior versions have a limited time which they continue to receive updates.

Upgrades only require the current version of Sage 100 or Sage 100c. All data is converted automatically. In most cases we recommend you consult with a qualified consultant to manage your Sage 100 or Sage 100c upgrades for you since they’ll be very familiar with the procedures and any special upgrade steps.

What Versions of Sage 100 Are Supported By Sage?

by

One of the more frequently asked questions about Sage 100 revolves around supported versions. Specifically, users frequently ask us what the officially supported versions of Sage 100 are.

 

Sage 100 Supported Versions

As of September 30, 2017, Sage actively supports ( link to KB document )  the following version with quarterly product updates (self-installing bundles of fixes/enhancements) – Sage 100/Sage 100c 207.

In addition, although not eligible for product updates, Sage 100/Sage 100c 2016, 2015 and 2014 are eligible for phone support and in some cases also product hot-fixes (at Sage’s discretion).

 

We recommend that you maintain compatibility with the version of Sage 100 which is eligible for product updates since those releases are typically first to get product fixes. It is also easier to install a product update which includes bundles of fixes than having to search for numerous hot-fixes and install those one-by-one.

An annual upgrade is advisable to maintain compatibility.

Sage 100 Supported Hardware and Operating Systems

We also are frequently asked about what operating systems – both server and desktop – are supported by Sage. In those cases, we always refer you to the Sage Supported Platforms Matrix which is updated periodically and displays the latest supported hardware and software configurations.

It is very important to review the Sage supported hardware and operating system list BEFORE beginning an upgrade. Microsoft Server 2008 and earlier are generally not supported and if you try to upgrade over these outdated versions you’ll receive a warning and the upgrade will stop.

Here is a link to the Sage 100 Supported Hardware and Operating Systems as well as information on the virtual environments supported with Sage 100.

 

 

Sage 100 Roadmap – May 2017

by

 

I’ve just returned from Sage Summit in Atlanta. This is a trip I had not expected to make but last minute plans were changed and I found myself on a plane to Atlanta where I  spent the better part of three days commuting by foot between the Hilton Atlanta and the Georgia World Congress Center, home of Sage Summit 2017 – Atlanta.

Sage Summit Road Ahead For Sage 100 and Sage 100c

Here’s a summary of the two-part session hosted by Sage to showcase planned developments for Sage 100 and Sage 100c. Before I begin, realize that the timeline and even features may change between now and the forecasted shipping date. Some features may be deferred or even dropped while others may be added.

Key Announcements:

Job Cost is moving to the framework (ETA Sage 100 v2018 due October 2017) – a quick self-running demo was given of what is referred to as Job Cost 2.0. From those who have seen the update in more detail, it has been described as more of a migration than a big re-write.

Payroll is also moving to the framework (ETA Sage 100 v2018 due October 2017). This is a project that was started not last Sage Summit but the one before. Sage have thrown a lot of  engineering power at this project which is believed to be one of their biggest internal programming efforts (Job Cost 2.0 was reportedly completed by one of Sage’s third party Master Developers)

Work Order is not yet scheduled to be upgraded to the framework but discussions have begun about who will do the upgrade and on what timeframe.

The remainder of the enhancements spotlighted on the roadmap appears to be integrations that will hook into Sage 100 or Sage 100c.

Sage 100 v2017.2 – ETA June 2017

  • Payroll 2.0 Limited Release
  • eInvoicing with Sage Payments Center
  • Beanworks AP Automation
  • Saget Budgeting & Planning integration

 

Sage 100 v2018.0 – ETA October 2017

  • Payroll 2.0 Generally Available
  • Bank Reconciliation- Auto Bank Feed
  • Office 365 Contacts Integration
  • Job Cost 2.0 Released
  • Inactive Warehouse Option

 

Sage 100 v2018.1 – ETA February 2018

  • Timecard to Framework
  • e-Commerce (Details TBD but likely third party integration)
  • Point-Of-Sale (Details TBD but likely third party integration)
  • BOTS – KPI Bots
  • Paperless Office to Office 365

 

 

What was shown during Sage Summit was very high level. There were few demos in the road ahead itself. In the final shipping versions it’s likely we will see further smaller enhancements that Sage have not listed on their larger roadmap.

These enhancements will be available to everyone who is active on a Sage 100 maintenance or Sage 100c subscription plan.

 

Which Versions of Sage 100 and Sage 100c Have Self-Updating Registration Keys?

by

As Sage rolls out their subscription version of Sage 100 – aka Sage 100c – they are also changing the way your registration codes are updated.

Previously, you would only need to change registration codes when adding or removing users or modules. Now, Sage automatically updates the registration codes approximately every 28 days.

This means if you are on a Sage 100c subscription and decide that you no longer want to subscribe that Sage will push updated keys to your system which turn the system to read-only mode. Further data entry will not be possible without a valid Sage 100c subscription.

Sage implemented a license key update program starting with Sage 100c v 2016 PU 2. There have been reported issues with the service, as it will lock out users if there is anything out of ordinary with keys.

Versions of Sage 100 and Sage 100c which auto-update keys:

  • 2015.5+
  • 2016.2+
  • 2017.0+

Even with Sage Update Advisor uninstalled and PEP turned off, license checks continued.

Per phone contact with Sage – the “update” program is using a URL to ‘phone home’. If the URL is blocked in anyway, it seems that it causes problems.

What Are The Differences Between Sage 100 and Sage 100c

by

 

Since launching Sage 100c 2016 in November 2015, Sage has been working overtime to make clear exactly what distinguishes Sage 100c from their Sage 100 product line.

Initially, the difference was:

  • Sage 100 = perpetual licensing
  • Sage 100c = subscription licensing

Sage 100c also offers a more modern user interface. This user interface was subsequently made available to Sage 100 users as well though they have less ability to tailor the UI than a 100c user.

Under the hood, the functionality between Sage 100 and Sage 100c is virtually identical. Third-party integrations which work with Sage 100 also work with Sage 100c.

Over time we expect the pricing for Sage 100 perpetual licensing to be equal or more than Sage 100c which will likely prompt most users to migrate to subscription-based Sage 100c.

As noted by Sage in their presentation, the following features are expected to be added into the Sage 100c product line only.

 

Available Now

  • Sage Inventory Advisor Basics (Requires Gold or higher maintenance)
  • 100c Manufacturing (Job Ops)
  • Enhanced Search
  • Multi-Bin (DSD / Scanforce)

Coming In 2017

  • AP Automation
  • eInvoicing
  • Budgeting & Planning
  • eCommerce
  • Auto bank feeds
  • Payroll 2.0 (also in Sage 100)
  • Sage 100 Anywhere
  • Paperless Office 365
  • Inactivate Warehouse
  • Mobile Sales
  • BOTS (Pegg)

 

TBD on Timing

  • Cloud Backup
  • Point of Sale
  • Inter-Company
  • Multi-Currency

 

Each of the above features or integrations, unless noted, will only be available for Sage 100c users.

 

Contact Us

Schulz Consulting
Connecticut Office
Phone: 833.724.3100
Email Us
Locally serving all of Connecticut, Massachusetts, Rhode Island, Vermont,
New York, New Jersey. Available remotely nationwide.
We are a local branch of DSD Business Systems Connecticut.