Browse by Tags

• .NET API
• ASP
• Code Snippets
• Context
• custom entity
• Default Values
• Document Drop
• entity level script
• eWareQuery Object
• External Script
• Fields
• Key Values
• Library
• Plugins
• Sage CRM 6.2
• Security
• Stored Procedure
• StoredProc
• table level scripts
• Validation
• Values() Collection
• Workflow

• A Universal "Go Back" button in Workflow

  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... Posted Nov 01 2009, 01:00 by Jeff Richards with | with no comments Filed under: ASP, COM, Workflow, create script, table level scripts, Fields

• Adding the Document Drop Plugin into a Custom Page

  This technique covers the use of the Document Drop ActiveX plugin within a custompage. The Document Drop Plugin is used within Sage CRM to allow the easy upload of documents to the library and will also... Posted Mar 30 2009, 10:43 by Jeff Richards with | with 4 comment(s) Filed under: ASP, COM, create script, custom entity, Key Values, Library, Document Drop, Plugins, 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

• Working with a Stored Procedure that returns a result set.

  I have discussed calling Stored Procedures from within Sage CRM before in the the article " Using the COM CRM.CreateQueryObj() to call a Stored Procedure ". From that article it can be seen that... Posted Feb 26 2009, 08:51 by Jeff Richards with | with no comments Filed under: COM, create script, eWareQuery Object, .NET API, Stored Procedure

• Using a Create Script to produce an automatically incrementing number.

  This example code is provided by a colleague in Switzerland. It provides an alternative way of creating an automatically incrementing field value. The result of the code is to create an incrementing number... Posted Feb 26 2009, 04:27 by Jeff Richards with | with 2 comment(s) Filed under: COM, create script, StoredProc, Default Values

• Using the COM CRM.CreateQueryObj() to call a Stored Procedure.

  Below is some code that illustrates how a Stored Procedure maybe invoked in the QueryObject. var strSQL = "DECLARE @@ret int"; strSQL += " EXEC @@ret=eware_get_identity_id 'notes'";... Posted Feb 09 2009, 02:03 by Jeff Richards with | with 3 comment(s) Filed under: ASP, COM, create script, External Script, eWareQuery Object, Stored Procedure

• 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

• Field Level Security and Create Scripts

  The control of field level security can be found against each field listed under the Field tab in the customization area. Administration | Customization | TableName We know from the documentation that... Posted Dec 21 2007, 10:00 by Jeff Richards with | with 2 comment(s) Filed under: COM, create script, Security, Fields

• Create a default value with a hidden field

  Thanks to Dave for this one! Problem: You want a date field to default to today when a user adds a new record to a table. You do not want the user to see the date field on the screen. Problem2: You try... Posted Dec 17 2007, 10:00 by Jeff Richards with | with no comments Filed under: COM, create script, Default Values

• 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