Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.
Browse by Tags
All Tags »
Sage CRM 6.0 (
RSS)
-
|
This article has been updated to correct the code. This is a little obscure but nonetheless this isssue caused me a problem this morning. I was just writing some code to put into the custom content box...
|
-
|
If you or your customers are using intelli-CTi for Sage CRM v6.0, and have upgraded to service pack e or above (hereafter referred to as Sage CRM v6.0e), please note that a new version of the CTI cab file...
|
-
|
I am going make the assumption you are working with Sage CRM 5.8 onwards. It is worth reminding ourselves that the security features in Sage CRM extend to cover the internal CRM reporting engine. If a...
|
-
|
Workflow rules in Sage CRM (5.8 or 6.0) can be based on Views rather than on simple tables. This is a feature that I find most useful when creating Escalation rules but we can also use views in the definition...
|
-
|
Sage CRM has a complex and sophisticated Security mechanism implemented as automatic alteration of the SQL used to fetch either the application data to the screen or the meta data that controls the availability...
|
-
|
This is one of the questions that can be quite hard to answer. Version 6.0 offers a good range of very important new features New Keyword Search and Advanced Search Functionality Simplified Field Level...
|
-
|
Reports and Report Charts can only be built from views. So If we want to create a Report Chart that uses Key Attribute Data then we must first create the view. The structure of the tables that holds the...
|
-
|
We can only actually support 'officially' versions of Internet Explorer that have been released at the time the CRM software is developed. So when CRM 5.7 was released only IE 55 and 6.0 were available...
|