SalesLogix Hot Fixes for the Web Client
22/06/10 14:04 Filed in: Hotfix | Web
Client
A word to the
wise-- Stay current with hotfixes
If you’ve been working with the Windows Client in Sage SalesLogix CRM for any period of time, you know that hotfixes come out all the time to address different defects. Most of the time, you can pick and choose which to apply. For instance, you can often apply HF3, then HF11, but you may choose not to apply HF5 as it doesn’t relate to how your company does its business.
But with the Web Client, each hotfix is based on the previous hotfixes. This means that you must apply them consecutively. You can’t skip any. So you must apply HF1, then HF2, then HF3, if what you really need is the fix that is contained in HF4. This can add up to a lot of work, due to customization retrofits, if you wait until you need a fix that comes out later on down the line.
Our suggestion is to try to keep up with the hotfixes as they are released, even if they are fixing a component that you don’t generally work with in the web client. Work them into your deployments as soon as you can, so that when a fix you’ve been waiting for does come out, you can get it implemented quickly with the least amount of work.
If you’ve been working with the Windows Client in Sage SalesLogix CRM for any period of time, you know that hotfixes come out all the time to address different defects. Most of the time, you can pick and choose which to apply. For instance, you can often apply HF3, then HF11, but you may choose not to apply HF5 as it doesn’t relate to how your company does its business.
But with the Web Client, each hotfix is based on the previous hotfixes. This means that you must apply them consecutively. You can’t skip any. So you must apply HF1, then HF2, then HF3, if what you really need is the fix that is contained in HF4. This can add up to a lot of work, due to customization retrofits, if you wait until you need a fix that comes out later on down the line.
Our suggestion is to try to keep up with the hotfixes as they are released, even if they are fixing a component that you don’t generally work with in the web client. Work them into your deployments as soon as you can, so that when a fix you’ve been waiting for does come out, you can get it implemented quickly with the least amount of work.