|
Browse by Tags
All Tags » Views (RSS)
-
If you find that your Indexing Server (Keyword Search) stops for any reason you may find that you get a message that looks like this: The CRM search index service has not been run since 21/12/2009. Please verify that the index service is configured correctly. If the message persists after an IIS reset...
-
My hope is that if you have attended any of my presentations about the Web Services interface for Sage CRM you will have taken away with you an impression of the importance of the design of the client application and how this would affect performance. The source code for the sample application 'sixthapp'...
-
One of the chief advantages of Sage CRM is that it is meta data based. The definitions of screens, lists and business rules like workflow are all stored in the database. If you change the definition in the database then it immediately changes the system with out need to recompile or otherwise 'deploy'...
-
The following is a survey of all the different articles that have discussed creating and editing views within Sage CRM. Understanding SQL views is essential as they under pin just about every feature within Sage CRM and completely determine what can or can't be done in Reports, Marketing Groups,...
-
You may need to reference data held outside of Sage CRM and within another application's database for a variety of business requirements including Reporting Graphing Reports within CRM are based on views and so if the SQL within a view can provide a way of accessing data in an external database then...
-
I orginally wrote about creating derived fields in a view in the article " Custom_Edits and Derived Fields Created in Views ". This discussion is a continuation of the ideas expressed in that article and will show how meta data definitions of a calculated field can be easily added into Meta...
-
You only need to follow the tags " List Page " or " List Block " to see that there have been lots of articles written already about how lists can be customized. In this article I want to step back and bring all these points together so we can see the range of options that we have...
-
It is a general rule that in CRM data fields are not supposed to hold HTML which can then be passed directly back to the interface. This is by design. So if you store a string in a text field like "<a href=http://dpp.sagecrm.com>http://dpp.sagecrm.com</a>" then when this is rendered...
-
Imagine you need to retrieve information from CRM via the webservices interface; this query should combine data from multiple tables. In the COM API (ASP pages, self service, table level scripts etc) you could use the QueryObject to build the exact SQL you need. var mySQL = "SELECT Person.*, Cases...
-
This was a recent question I got from a business partner. When you create a derived field in a SageCRM SQL View how do you get SageCRM to see this field as a numeric so you can sum the field within SageCRM reports? This is a great question. But there are some parts of this question that need explaining...
|
|
|