Sage CRM 2018 R3: Changes in supported software

Hints, Tips and Tricks

Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.

Sage CRM 2018 R3: Changes in supported software

  • Comments 1
  • Likes

As a general rule, we only support products that themselves enjoy mainstream support from their manufacturers.  This means that our software inevitably changes over time.

We need to consider the changes in supported software.  This affects not just the servers but also the devices that are used to access integrated Sage CRM.

WHAT’S CHANGED

Database server

  • Microsoft SQL Server 2016 SP1 changed to Microsoft SQL Server 2016 SP2

Note:

2018 R3 was tested with SQL 2014 SP2
2019 R1 will also be tested with SQL 2014 SP2

Mobile devices

  • iOS 11 changed to iOS 11.x

Web browsers

  • Support for Apple Safari on desktop computers (macOS and OS X) removed
  • iOS 11 changed to iOS 11.x

Although the QA team did cover the Safari browser on Mac OS in their regression testing (And the exact version tested of Safari was 11.1.1(11605.2.8) ) – we aren’t going to be testing Safari in the future and so support for Safari has been dropped.  This is because of the low number of users using Safari as their browser of choice.  Please note that this should not negatively impact users of Apple Macs, because Chrome and Firefox are available on Apple Desktop and Laptop devices.

Comments
  • Within this article it states “we only support products that themselves enjoy mainstream support from their manufacturers”.  As far as I am aware according to Microsoft (support.microsoft.com/.../1044) SQL Server 2014 Service Pack 2 is still under mainstream support.

    I understand that with CRM there is policy to support the latest two releases of software.  However as both SQL 2016 and SQL 2017 were released in quick succession this policy seems a little too restrictive.  SQL Server 2016 (which is the oldest version of SQL server you will support) was release 1st June 2016.  This being the case a server which was commissioned a little over two years ago could require a major upgrade in order to meet the new system requirements.  In my experience most clients have a server refresh every three to five years, certainly not every two.  For some clients this will be a very expensive exercise, especially considering that SQL 2014 is still supported by Microsoft.  In addition you are adding confusion by still supporting SQL Express 2014, which is a restricted version of SQL 2014.