View more results: All Community | Partner Community
  • 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: An example of a Table Level Script showing update of data not submitted from browser

    I have discussed how the Values collection can be used to correct inbound data in the article " Correcting inbound data using Table Level scripts and Values() collection ." This is a further example of how the Values collection can be used. The code sample is from a Table Level script on the...
  • Blog Post: A Trick to Identify in Code which User has been Changed in the User Administration Screens

    Working within the System Admininstration screens can present its own challenges. Please see the article " The SQL Tab Clause and the User Admin screens " for an example of what I mean. Consider if I am working within a the System Administration screen and I want to trigger a set of behaviour...
  • 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...
  • Blog Post: Sending an Email from a Table Level Script

    Consider this scenario. When an Opportunity is reassigned then an email needs to be sent to the newly assigned user. The Table Level Script needs to fire correctly whether a single Opportunity is reassigned through the user interface or whether a batch of Opportunities are reassigned by another...
  • Blog Post: 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 the workflow is usually handled by looping. We can see from the diagram below how a workflow...
  • Blog Post: Using Hidden fields to detect which System Action triggered a Table Level Script.

    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...
  • Blog Post: How can I get the SID in Serverside scripting?

    The SID is the session ID value. The SID may be wanted if you are building a string that represents a hyperlink that will be returned to the browser. The SID after all only is needed for a new web request, we do not actually need it within server side scripts normally as there we are already in the context...
  • Blog Post: The eWareQuery Object: A warning.

    I was going to call this a 'warning from history' but as you read the rest of the article you may realise that the 'updateddate' may never have been filled in. The eWareQuery object is a fantastically useful tool for on-premise developers to use in ASP pages, table level scripts and...
  • Blog Post: Collecting Information from Checkboxes in TableLevel Scripts

    A customer had a requirement to add a series of check boxes to the Lead screen. The check boxes would allow the user to quickly classify and collect the different interests of a prospect as it the new Lead was entered into the system. Once the lead was saved a summary of the interests then needed to...
  • Blog Post: A round up of essential articles on setting up and using Table and Entity Level Scripts

    Table and Entity Level Scripts can be thought of as a bit like SQL triggers. They allow a developer to create scripts that are run when certain database interactions take place. They are defined as javascript and stored in meta data. The scripts are then executed when a record is inserted, updated, or...
  • Blog Post: Uploading Leads with Notes using Table level Scripts

    Recently, we had a requirement where a client wanted to upload Leads with Notes. The way Data upload works for leads, we cannot map any field from upload file to tables other than the lead entity. Hence, we came up with below solution. Requirements 1. To be able to upload lead along with notes...