This document has been made available for development partners. This covers version Sage CRM 6.2. We are pleased to announce the release of the 'Sage CRM Quick Start Performance Guide'. The idea behind this Guide is to provide you with some quick hints and tips to try to optimize CRM performance...

This has been written using Sage CRM 6.2d and will look at the behaviour of the Values collection. For a more complete discussion see the article The Values() Collection . Imagine a new field called pers_type has been added to the person table and included to the screen personboxlong. The field pers_type...

A customer needs to know what particular System Action was used to trigger a Table Level Script. The big problem facing us in this scenario is that the Values() collection usually used in server side scripts to obtain variables passed in from the browser can read any form data but it can not read information...

This article has been edited (1st November 2009) to correct links and make the code follow the convention introduced in Sage CRM 6.2 The requirement to allow the user to fall back to an earlier point in the workflow is usually handled by looping. We can see from the diagram below how a workflow can allow...

The code on this page was corrected 31st October 2009. Tablescripts are great, they allow you to add code to Sage CRM which will always fire when a table event happens, for example, the company is updated. Look in the developer/admin guides for more details on them. The problem is that you may find that...

Any SQL statement may take time to run and result in a timeout error. In Sage CRM the general timeout period is controlled within the Administration -> System -> Database screen by setting the Query Timeout field value. This is expressed in seconds and represents the maximum amount of time that...

This article was updated 31st October 2009 to correct hyperlinks. Detached TableLevel Scripts are created in the same way as TableLevel scripts, except you select Detached Table Level from the Script Type list when completing the Table Script details. Unlike TableLevel scripts, Detached Table Level scripts...

If you are developing a server-side script such as a Create Script, Validate Script or Table Level Script, it is often useful to write debugging information to a log. Jeff has blogged about a technique for doing this using the Scripting.FileSystemObject. I'd like to share with you a very simple function...

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

This article was updated on 22nd May 2009 to follow the coding convention introduced in Sage CRM 6.2. The Values() and FormValues() collections are serverside objects that are analogous to the ASP Request.Form() and Request.QueryString() collections. In an ASP page we can see the submitted values of...