04-30-2013 12:35 PM
Looking for some clarity on the correct updates to install.
Web Core and Web Model are cumulative and should be installed on both new installs and upgrades with the caveat that Web Model will potentially break customization, correct?
SNC Updates (Update 00, etc.) are not cumulative and are the equivalent to HotFixes in the old terminology, correct?
Should all of the SNC updates be applied for a new install or fresh upgrade? I understand Update 00 is only applicable to a system that is upgrading from 7.5.4 and not a previous version.
04-30-2013 01:06 PM
05-01-2013 12:00 AM
Beware of one other important, but easily missed, change.
It used to be that with SNC fixes (hot-fixes) that they would replace one HF with another should the components in one change the other (e.g. the provider, controls, saleslogix.exe for example).
Now, they do not.
So, if you look at SNC 02 - notice it replaces saleslogix.exe plus slxcontrols.ocx. If you look at SNC 08 - it also replaces saleslogix.exe - but does not contain the slxcontrols.ocx (the doc does mention that 02 is a pre-req).
This means, from now on, you have to ensure you update all and in order - otherwise, you will have mixed versions.
05-06-2013 04:57 PM
In the 7.2x series they missed the OCX changes as well....so Architect/Admin only installations never had the new OCX's which were installed in the Client only installations......
05-06-2013 05:12 PM
Yes, but this seems now to be deliberate. Previously, each HF could potentially replace a prior HF (meaning you could discard the prior one).
For example, if slx.exe was replaced in one hot-fix then the next hf would deprecate the other. The document now mentions that x relies on y - so, basically, you have to apply them serially.
As I understand it - this is to reduce the size of the hf and to remove the need to know what replaces what. Unfortunately, brings in just a different issue in that hot-fix (or SNC) 59 will require 58 other updates - all to be done individually :-)
05-06-2013 06:07 PM
OK.. so what has to happen (based on what you say..) is Updates have to be released "serially" and cannot skip as they have in the past.. that is:
SalesLogix cannot release Update00, Update01, Update04 .. and than later Update03 .. followed by Update02 some time later.
However, what I just said is precisely what has happened - they are NOT being released "in order".
05-06-2013 11:52 PM
No. There is a distinct difference this time.
A hot-fix fixes a particular issue. That we know. So, they may get several hot-issues and assign a HF number e.g. 3, 5, 7 as they are assigned to dev to be fixed. However, they may release in any order e.g. 7,5,3 depending on how quickly they are fixed. That was always the case.
If, however, when they came to release the hot-fix it superceded a prior release then the components within each HF were also contained in the latest release. See here for examples (the struck out items): http://www.empath-e.com/support/slx_v75. The example is Hot-Fix 16 replaces and includes Hot-Fix 11. The document says that on page 1 "Update 16 for Sage SalesLogix version 7.5.4 contains one newly-fixed issue and two fixes released in previous hot fixes." and "Previously fixed and released in Update 11 for Sage SalesLogix version 7.5.4"
But, this time, SNC 8 came after SNC 2 but does not include SNC 2. You have to apply both and the document says this "
requires Sage SalesLogix 8.0 Update 02". Under Pre-Reqs.
So, there is a difference - quite a major one. I suspect that they must also be assigned by date order (earliest first) rather than by number e.g. 01,02,03 probably won't be the case (it is currently).