Outlook Conditions Not Syncing
Keep conditions
concise and limited in number
If you are having a problem using Intellisync for bi-directional syncing of contacts betweem Outlook and Sage Saleslogix CRM, make sure that the conditions associated with account groups are concise and limited in number. We have run into situations in which having more than 50 or more conditions would result not only failure to sync in both directions but also the loss of contact data. When conditions were trimmed down to fewer than 5o the problem went away. Moral: Simple is always better.
If you are having a problem using Intellisync for bi-directional syncing of contacts betweem Outlook and Sage Saleslogix CRM, make sure that the conditions associated with account groups are concise and limited in number. We have run into situations in which having more than 50 or more conditions would result not only failure to sync in both directions but also the loss of contact data. When conditions were trimmed down to fewer than 5o the problem went away. Moral: Simple is always better.
SalesLogix Hot Fixes for the 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.
The Importance of Managing Indexes
01/07/10 17:10 Filed in: Tech Topics
| indexes
We all know that database indexes
help speed up queries against the data, by keeping track of where
records are by certain fields. For instance, fields that get
queried a lot should be indexed to help with performance, and
fields that often have the same data in them are good to index, so
that they can be sorted and grouped together.
There is another important reason to create indexes. In the web client, data grids without indexes sometimes reorder themselves in strange and incomprehensible ways. This can be very disconcerting, to say the least. Add a few indexes on the fields that seem most logical and the data will start behaving itself. It will remain in the exact same order each time it gets queried and refreshed.
So if you’re seeing any strange happenings with your data grids, reviewing your indexes is a great first step in troubleshooting. It might be as simple as adding a few indexes. And the bonus is that your performance should also increase as well.
There is another important reason to create indexes. In the web client, data grids without indexes sometimes reorder themselves in strange and incomprehensible ways. This can be very disconcerting, to say the least. Add a few indexes on the fields that seem most logical and the data will start behaving itself. It will remain in the exact same order each time it gets queried and refreshed.
So if you’re seeing any strange happenings with your data grids, reviewing your indexes is a great first step in troubleshooting. It might be as simple as adding a few indexes. And the bonus is that your performance should also increase as well.
