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'...

I have previously provided an example of a function that may be used in a search screen to test whether the page contained a List or a Grid. You can see this in the article " Clientside control of fields in Search screens including detection of grids and lists ". This is only part of a short...

This tip is a modified product of a conversation that took place between a couple of my colleagues in the UK and US. The need was to find a technique that would allow the easy clientside control of fields with the search screens. It had to be clientside because the technique was needed for the hosted...

This article shows how to add a button to an existing system screen that will call a report. For example if you look at the image of the OpportunitiesList screen below you can see that a button has been added that calls a popup window that displays a pdf report. You may think that since reports are a...

A while back I blogged about injecting scripts into system action screens that don't have custom content field. Well recently I had an epiphany about Translations and using them to embed scripts into screens where there is no custom content field. The technique described in this post is a lot easier...

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...

Throughout the system, in different screens, Sage CRM uses tooltips on hyperlinks. For example in the OpportunityList screen you can see tool tips on on the tab customization button at the top right and when you hover over the status of the opportunity. This hyperlinks are produced by ALT properties...

A screen like the company summary screen has a very particular structure because it is partially defined in meta data and partial has its structure hard coded into the system action being called. The detail of this is discussed in the article " Changing a Summary Screen (e.g. Company Summary Screen...

The code in article has been corrected, 7th May 2009. An individual screen within CRM will be produced as a result of a hyperlink that looks like this: http://servername/crm/eware.dll/Do?SID=5351668533575&Act=166&Mode=1&CLk=T&Key0=4&Key4=4&Key27=80&T=New I wrote a little while...

This article has been updated (29th April 2009) to use the coding convention introduced in Sage CRM 6.2 If you have started to code with Sage CRM you will know that the world is seemingly divided into two, ServerSide and ClientSide. The objects and properties that we can use ServerSide can not be used...