Browse by Tags

• ASP
• Code Snippets
• COM
• Context
• CurrentUser
• Custom Content
• customization
• entity level script
• Fields
• onChange
• Registry
• Reports
• Sage CRM 6.2
• Search Screen
• SQL
• table level scripts
• Values() Collection
• Views
• Workflow

• 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... Posted Aug 24 2009, 10:07 by Jeff Richards with | with 4 comment(s) Filed under: Custom Content, Workflow, create script, table level scripts, SQL, Views, Reports, onChange, Validation, Fields, customization

• 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... Posted May 22 2009, 05:00 by Jeff Richards with | with no comments Filed under: create script, table level scripts, Validation, Values() Collection

• 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... Posted Mar 13 2009, 07:23 by Jeff Richards with | with no comments Filed under: COM, Workflow, create script, table level scripts, Validation

• 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... Posted Mar 13 2009, 07:19 by Jeff Richards with | with 7 comment(s) Filed under: COM, create script, table level scripts, Validation, Values() Collection

• COM Coding Standard Change in Sage CRM 6.2

  Please note there has been a coding standard change between Sage CRM 6.1 and Sage CRM 6.2. The instantiated COM object in Sage CRM 6.2 now has an alias of "CRM" rather that "eWare"... Posted Oct 15 2008, 10:16 by Jeff Richards with | with 2 comment(s) Filed under: ASP, COM, entity level script, create script, table level scripts, Validation, Code Snippets, Sage CRM 6.2

• 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... Posted Apr 02 2008, 10:00 by Jeff Richards with | with 1 comment(s) Filed under: create script, table level scripts, Validation, CurrentUser

• Field Level Scripting in Search Screens

  Imagine the situation where there may be a problem with allowing users to search against a entity with out putting in at least one search criterion. You may find the searching against companies too slow... Posted Dec 22 2007, 10:00 by Jeff Richards with | with no comments Filed under: create script, Search Screen, Validation, Fields, Values() Collection

• 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... Posted Nov 23 2007, 10:00 by Jeff Richards with | with 1 comment(s) Filed under: create script, table level scripts, Registry, Validation

• Getting Hold of User Information in Code

  If you need to control the display of screen elements like buttons in ASP pages (or even client side in the browser screens) according to the identity of the CRM users then you will obviously need to be... Posted Oct 28 2007, 10:00 by Jeff Richards with | with no comments Filed under: ASP, COM, create script, Context, Validation