View more results: All Community | Partner Community
  • Blog Post: Injecting javascript into system action screens with no Custom Content field

    ** Note a better technique is described in this blog post ** One of the very nice features of CRM is the Custom Content field on screens. They allow you to enhance the functionality of screens and add business logic to be processed client-side, making for a smoother user experience. But there are...
  • Blog Post: Adding Dedupe Behaviour to the Lead Entity

    This article has been updated to ensure the variables that are passed can take into account a wider range of characters in passed names including umlauts, accents and cedillas. Although this article describes a technique for adding dedupe behaviour to the Lead table it may be adapted for other entities...
  • Blog Post: Adding a Report Button to an Existing System Screen, e.g. OpportunitiesList (for Sage CRM v7.1sp2 and earlier)

    Note: This article discusses techniques relevant for Sage CRM v7.1sp2 and earlier. If you are using Sage CRM 7.2 please refer to the articles that discuss the new Client Side API. This article shows how to add a button to an existing system screen that will call a report. For example if you look...
  • Blog Post: The Client Side CurrentUser object

    In every screen (entrygroup) where you can add javascript (<script>) into the custom content box you can reference the clientside CurrentUser object. You can see that this has been used in several articles in the blogs such as " Controlling Buttons using Client Side code " And other...
  • Blog Post: The Clientside Control of Lists and Columns (for Sage CRM v7.1 and earlier)

    Note : This article discusses techniques relevant for Sage CRM v7.1 and earlier. If you are using Sage CRM 7.2 please refer to the articles that discuss the new Client Side API. I have previously provided an example of a function that may be used in a search screen to test whether the page contained...
  • Blog Post: Stopping Double Clicks in Workflow Screens (for Sage CRM v7.1sp2 and earlier)

    Note: This article discusses techniques relevant for Sage CRM v7.1sp2 and earlier. If you are using Sage CRM 7.2 please refer to the articles that discuss the new Client Side API. This article was prompted by a customer requirement to prevent over-zealous users repeatedly clicking on the save button...
  • Blog Post: Adding extra behaviour to Client Side code

    This article has been updated to correct links . If you have been creating onChange scripts then you will possibly about know the quirk which requires you to use single quote marks (') rather than double (") quote marks when outputting strings. e.g. window.alert('this field has changed'...
  • Blog Post: Another Trick for Grabbing Key Values in Client Side code

    The code in article has been corrected, 7th May 2009. An individual screen within CRM will be produced as a result of a hyperlink that looks like this: http://servername/crm/eware.dll/Do?SID=5351668533575&Act=166&Mode=1&CLk=T&Key0=4&Key4=4&Key27=80&T=New I wrote a little...
  • Blog Post: Making tooltips work in Firefox, Chrome, Safari, Opera et al... in Sage CRM v7.1 SP1 and earlier

    Note: This article refers to versions of Sage CRM earlier than Sage CRM v7.1 SP2. Sage CRM v7.1 SP2 adds support for Firefox, Chrome and Safari browsers and tooltips appear automatically in the screens. Throughout the system, in different screens, Sage CRM uses tooltips on hyperlinks. For example...
  • Blog Post: Managing Client Side Code in Sage CRM (for Sage CRM v7.1sp2 and earlier)

    Note: This article discusses techniques relevant for Sage CRM v7.1 and earlier. If you are using Sage CRM 7.2sp2 please refer to the articles that discuss the new Client Side API. How do we manage our client side script in Sage CRM to maximise our ability to maintain the code ? For those new to...
  • Blog Post: How do default addresses and persons get created for a Company?

    When you create a new company using the standard system behaviour the Address and Person contact details that you provide get recorded into their separate tables and foreign key references are recorded on the company table to indicate which address and which person are default for that company. The foreign...
  • Blog Post: Clientside control of fields in Search screens including detection of grids and lists

    This tip is a modified product of a conversation that took place between a couple of my colleagues in the UK and US. The need was to find a technique that would allow the easy clientside control of fields with the search screens. It had to be clientside because the technique was needed for the hosted...
  • Blog Post: Adding Clientside Code into Dynamically Built Workflow Action screens

    I had a conversation with a participant at one of the recent Bootcamps regarding the use of clientside code in dynamically built workflow screens. This topic has also appeared in the Forums with the community site. The partner's customer had a requirement that when a user was processing an opportunity...
  • Blog Post: More about Screen Mode (for Sage CRM v7.1sp2 and earlier)

    Note: This article discusses techniques relevant for Sage CRM v7.1sp2 and earlier. If you are using Sage CRM 7.2 please refer to the articles that discuss the new Client Side API. I have only just written about Mode and how to tell whether you are in the Edit or View state of a screen in the article...
  • Blog Post: AJAX and the whole Web 2.0 thing.

    I wrote in an article about Self Service some time ago "I get the sense that there is a growing interest in the construction of Customer Portals and the general Web 2.0 'buzz' where people need to bring all types of data up into customer facing applications that blend information and...
  • Blog Post: Customizing Progress Screens when Workflow Switched Off (Lead/Opportunity/Cases/Solutions)

    There are 4 core entities in the system that have progress tables. Lead Opportunity Cases Solutions There are default workflows provides for these entities and in most implementations of Sage CRM the powerful feature of the graphical workflow engine will be used. This is found...
  • Blog Post: Changing a Summary Screen (e.g. Company Summary Screen)

    A summary screen (like the company summary screen) is not easily changed. It is partially constructed from EntryGroupBlocks defined in meta data and other screen components that derive from hard coded elements within the dll. The Company Summary screen calls the CompanyBoxLong, AddressBoxShort, and personBoxShort...
  • Blog Post: Adding a new Panel to a Summary screen e.g. Company Summary

    A screen like the company summary screen has a very particular structure because it is partially defined in meta data and partial has its structure hard coded into the system action being called. The detail of this is discussed in the article " Changing a Summary Screen (e.g. Company Summary Screen...
  • Blog Post: Making the top tabs static

    Here's a little tip that may be handy for those of you who are by necessity or inclination members of the all-on-one-screen school of user interface design. By default, if you have to scroll a screen in Sage CRM the top tabs will move along with it. This can be problematic for two reasons: ...
  • Blog Post: Making ServerSide objects available to ClientSide code (onChange and Custom Content scripts)

    This article has been updated (29th April 2009) to use the coding convention introduced in Sage CRM 6.2 If you have started to code with Sage CRM you will know that the world is seemingly divided into two, ServerSide and ClientSide. The objects and properties that we can use ServerSide can not...
  • Blog Post: Doing some simple math with onChange

    My buddy and also fellow author on this blog Rob needed some math to be done on a screen. Together we came up with this nice simple example that would take care of this task by using the onChange event of a field. To test this add 3 fields to any entity, I chose the company entity for my demo. My fields...
  • Blog Post: attachEvent and addEventListener in client side scripts

    Within clientside code for Internet Explorer if you use multiple <SCRIPT FOR=WINDOW EVENT=ONLOAD> then these will over write each other. You can test this out in a screen like the Company Summary screen. Add the following into the CompanyBoxLong custom content. <SCRIPT FOR=WINDOW...
  • Blog Post: Including a JavaScript file in CRM screens

    OK, so lets say you have a bunch of javascript functions that you have put into a js file to use on multiple screens, or you want to use a 3rd party javascript library such as jQuery , prototype or scriptaculous with Sage CRM. How do you get the library/libraries loaded? Here are a couple of snippets...
  • Blog Post: Intelligent Selects

    Fields such as the user selection list (oppo_assigneduserid) are examples of a type of field known as an Intelligent Select The intelligent select in edit mode displays additional structures, a search box and a magnifying glass image. The search box associated with the intelligent select or user select...
  • Blog Post: How can I redirect to another screen immediately after entering a record? (for Sage CRM v7.1sp2 and earlier)

    Note: This article discusses techniques relevant for Sage CRM v7.1sp2 and earlier. If you are using Sage CRM 7.2 please refer to the articles that discuss the new Client Side API. This article has been prompted by the following business requirement. A customer needed to immediately redirect to the...