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: Correcting inbound data using Table Level scripts and Values() collection

    Occasionally we need to be able to correct data that has been submitted to bring it within tolerance. An example of this maybe where someone has chosen a customer credit limit level that is too high and we need to change this to the maximum allowed value based on the customer current outstanding orders...
  • Blog Post: Interacting Table Level Scripts: A Chain Reaction

    Consider this scenario. There is an UpdateRecord() event function in a TLS on the Company. When the Company assigned user is changed (comp_primaryuserid) then all the 'In Progress' opportunities belonging to that company are reassigned to the new company account manager (oppo_assigneduserid...
  • 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: 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: Handling the Data in Multi Select fields in Validate Rules and Table Level Scripts

    This has been written using Sage CRM 6.2d and will look at the behaviour of the Values collection. For a more complete discussion see the article The Values() Collection . Imagine a new field called pers_type has been added to the person table and included to the screen personboxlong. The field pers_type...
  • 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: 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: 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...