View more results: All Community | Partner Community
  • Blog Post: The Values() collection

    This article has been edited and corrected. The code in this article has been changed to follow the coding convention that was introduced in Sage CRM 6.2 The Values() collection can be used in all serverside scripts to examine the passed in Values from a form. Create Scripts Validate Scripts...
  • Blog Post: CurrentUser object in Serverside Code

    The CurrentUser object can be used in all serverside code including Create Scripts, Validation scripts, Table Level scripts and Workflow javascript conditions. It provides information about the current user session. You can list the properties of the CurrentUser object by using this snippet of code in...
  • Blog Post: More about the Values and FormValues collections

    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...
  • Blog Post: Creating Global Code for OnCreate and Validate scripts (Internal COM API)

    There have been several articles written about using the scriptcommonfunction registry key to set a global function library for tablelevel scripts, but this option is not available for the other internal scripts. So if we can't use the function library of the tablelevel scripts to create globally...
  • Blog Post: Validation rules don't always mean "Stop!"

    This article has been updated to follow the coding convention that was introduced in Sage CRM 6.2 I was asked recently about how to create a log of when data was changed within a particular screen. Now the requirement was focussed on the screen and not on the the record. If we had been interested...
  • Blog Post: Adding Additional Custom Logs to Sage CRM

    If you are working on an integration of Sage CRM with another system you may have a requirement to Log errors that are specific to the integration itself. For example integrating Sage CRM with an ERP system you may wish to report errors fully so that possibly several lines worth of info) is logged to...
  • Blog Post: Objects Available in the Internal COM API

    The diagram below contains the objects, methods and properties that are the main ones used in the internal COM API of Sage CRM. These objects can be used in field level scripts; Create and Validate and also in TableLevel scripts and Workflow JScript conditions. The are sometimes...
  • Blog Post: Reporting on Customizations

    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'...
  • Blog Post: Validation of Dates

    The validation of dates can be tricky. Partly this is due to jscript and partly down to the flexibility that Sage CRM provides in allowing dates to be presented. I have covered how default values dates can be controlled in the article: Populating Default Date Field Values Other Date related articles...
  • Blog Post: Validating Phone Numbers and Email Addresses

    This post has been edited (29th April 2009) to using the coding convention introduced in Sage CRM 6.2. If you have explored this idea in Sage CRM you will probably have discovered that the peculiar structure of the phone and email screens means that the regular options for screen based rules are...