Browse By Tags

  • Blog Post: The Client Side API

    This is a simplified and specialised set of code libraries that will allow easy screen customizations. The API is based on the JQuery syntax although I must stress that knowledge of JQuery is not needed in order to use the API. The API is included as part of the full product development cycle and...
  • Wiki Page: 492-17065 - Setting an onload event may result in a CRM screen not rendering

    Summary: Adding an onload event via a Custom Content script may result in a CRM page remaining blank after loading. This is caused by the script replacing the onload events. Symptoms: A customer added a Custom Content script in the following format: <script> window.onload = function(){ alert("The...
  • Wiki Page: 492-17089 - Long loading times on Workflow and Line Item screens

    Summary: Users may experience a delay when attempting to load screens that are launched using the jQuery load() function. This includes the Workflow and New Line Item screens. Symptoms: Poor performance may be seen when loading certain screens, especially when the user is not accessing CRM on a local...
  • Wiki Page: 536-17173 - Missing vertical scrollbar in custom ASP page

    Summary: On a custom ASP page that contained an iframe there were issues with the scrollbars on the iframe because of the javascript in the asp page was attached to the window.onload event. Cause: For example if you bind to the onLoad event using javascript: window.onload = function() { doLoad(); } It...
  • Blog Post: Rewriting an existing business rule to use jQuery

    This article is going to walk through the process of converting a business rule originally coded for Internet Explorer to one that uses the jQuery javascript library to work in all browsers. This article uses as its base the business rule originally discussed in the article " Controlling Buttons...
  • Blog Post: Sage CRM 2017: Performing arithmetic functions on Currency fields within the browser (Adding fields and creating a total).

    A customer had a requirement to sum the value of two currency fields and place the calculated total in a third field. See the image below. The three new fields in my example are oppo_licensevalueestimate oppo_servicevalueestimate oppo_totalvalueestimate Each have been defined...