The planned re-engineering of Sage 300 CRE

Prepare for the future of Sage Construction and Real Estate

by Kyle Zeigler, Sage Senior Certified Consultant

Learn the version prior to installation!

Sage’s gradual re-engineering of the Sage 300 Construction and Real Estate accounting product began with the introduction of the new Sage Desktop in version 16.1. As the transformation continues over the next few years, users are encouraged to become well-informed of the changes introduced in each new version before installing it. Proper preparation and planning for the new versions will save users the unnecessary downtime and expense of troubleshooting the software when unexpected issues arise after installation.

The SQL choice

For instance, with version 17.1, users have the ability to replicate their Sage 300 CRE data into a Microsoft SQL database, which in turn allows integration with Sage’s new mobility applications (Sage Construction Project Center and Sage Service Operations). However, to take advantage of this new feature, Microsoft SQL Server must also be installed. SQL Express can be used at no additional cost, but there are limitations on the size of the data that can be replicated. Users who want to replicate large quantities of data may need to purchase a full version of MS SQL. IT providers should be made aware of the new requirements so that any potential need to upgrade computers, software, and/or operating systems can be budgeted well in advance.

New License administration tool

Also, users should be aware of the new License Administration tool in version 17.1. Licenses can be allocated across multiple servers or to allocate licenses for mobile applications to users. If licenses are not properly allocated after installing version 17.1, users will not have access to the applications in their Sage 300 CRE suite.

Prior to installing version 17.1, the following preparation is recommended:

  1. Review the minimum hardware and software requirements for both servers and workstations with your IT provider to ensure the newer version will be supported on your network.
  2. Clean up the Sage 300 CRE data folders. Use File Tools to move corrupt or renamed files that are no longer needed. Move non-data files such as Excel, .pdf, print files, .txt files, etc. to a location outside of the data folder. Do not delete files! Move them to a folder marked for deletion at a future date (like a year from now), just in case you discover a file needs to be moved back.
  3. If you use the PJ correspondence log and the Correspondence folder is inside the data folder, work with your Sage certified consultant to move the folder to a new location outside of the data folder. Do this for your Printouts folder too. This will reduce the size of your data folder and make it much easier to use File Tools to back up your data folder.
  4. Move data to History files or archive folders. When upgrading data in version 17.1, every record in the database must be upgraded. This can take considerable time. When data is split between the current and history transaction files, the upgrade process can be split into two or more sessions, shortening the time before users can log back in.
  5. Make a File Tools backup of the data folder and then run File Doctor to compress good files and fix and compress bad files. Schedule this for an evening or weekend! Depending on the size of your data, this can take several hours to complete.
  6. Allow plenty of time to upgrade your data after installing the new version. As mentioned, every record in your database must be upgraded after installing version 17.1. Users will not have access to the software during the installation and upgrade process.

Steps 1 through 5 can be completed well in advance of the new version installation. If you complete your annual upgrade with the assistance of a Sage certified consultant, or if you require assistance preparing your data for the upgrade, you are especially encouraged to schedule time with your consultant well before the date you plan to install the newer version (even months in ahead). With these steps completed in advance, your version upgrade can be completed quicker and with less potential for unexpected issues.