View more results: All Community | Partner Community
  • Blog Post: Using a Table Level Script to Track Changes to Data Made by Users.

    This article uses an idea first mentioned in " Validation Rules Don't Always Mean Stop! ". The example 'UpdateRecord' event function below will write out into a log file which fields have changed. It won't write every field in the screen so we first need to know what fields...
  • Blog Post: Write to the CRM logs in a server-side script

    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...
  • Blog Post: How do you know if your Table Level Scripts are being executed?

    Hi all, Something I've come across time and time again is where people are not sure if their Table Level Scripts are being executed. It's difficult to see where you went wrong on your table level script if you're not even sure whether it has been executed or not. Furthermore if you...
  • 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...