View more results: All Community | Partner Community
  • Blog Post: Zip Check

    This is a little mod I came up with after adding in a few addresses in CRM. In this day and age of modern technoligy why in the world would we have to type in the City and the State if we know the Zip? I mean really, think of the time you will save by having a tool that could help with this. OMG think...
  • 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: Controlling Top Content

    Above is a screen shot that shows a default opportunity summary page. At the top of the page is the frame that contains the TopContent information. Sometimes this is called the context information. In this screen the TopContent brings in data from the Opportunity, the Company and the Person entities...
  • Blog Post: Using an onChange Script on a Selection list to set a value of another field

    This is a simple real world example. There was a customer need to set a field values based on value of another field on the opportunity screen. The screens had been customized. The oppo_forecast and oppo_certainty fields were removed from the opportunitystatusbox and oppo_certainty was added to the...
  • Blog Post: How do I hide the 'Follow-up' check boxes on a New Appointment or New Task Screen Screen?

    Below is a screen shot that shows the New Task Screen. You'll see there are some checkboxes that if selected will launch another new communication screen once the New Communication is saved. The HTML that generates these Checkboxes looks like this: <TABLE CLASS=VIEWBOXCAPTION><TR><TD><TD><input...
  • 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: Example Business Rules for Text fields.

    Below are some code examples showing how Business Rules can be implemented on Text fields using the onChange and Validation script options within a screen. Note: Only the onChange examples can be used within a hosted (SageCRM.com) implementation. The examples shown are: The field may only...
  • Blog Post: Regular Expressions in Rules

    I was just answering an email about how a consultant could create a business rule that ensures data entered by the user matches a particular pattern. The specific example was needed to confirm that the code entered into a text field was only numeric and didn't include alphabetic characters. I had...
  • 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: Dynamically change SearchSQL for an SSA field client-side

    Recently I was asked if it is possible to restrict a Search Select Advanced field based on criteria that may change client-side. The answer was no, it's not possible through standard customization. However it's not impossible... I want to be very upfront about this blog post: it is about an...
  • 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: Fine Control of PopUp windows (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. In the article " Using Clientside Code to Change the Property and Behaviour of a Column in a List " I gave an...
  • 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: Controlling Buttons using Client Side code (Sage CRM v7.1sp2 and earlier)

    It is a fairly common requirement to need to remove buttons from existing system screens in particular circumstances. For example there might be an organisational business rule that says that only assigned owner for a Lead should be able to access the 'Convert to Opportunity' button. Since...
  • Blog Post: Jack's Hack FAQ

    hack [hāk] -verb (used with object): To cut, notch, slice, chop, or sever (something.) To damage or injure by crude, harsh, or insensitive treatment; mutilate; mangle. -computing jargon: A quick job that produces what is needed, but not well. To alter the intended...
  • Blog Post: Getting server side stuff client side (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. In this post I will be exploring the possibilities of combining the CRM.AddContent method and some javascript data transmission...
  • 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: Grabbing Serverside Information using a SOAP Webservice call (AJAX)

    Please note that this is only a part worked solution. I have added this to show how an web service request can be made from a client to extract any information (available to web services) that is needed from the server. This example is based on code that is discussed within the Developer training...
  • 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: Sage CRM 7.2: Creating and Using ASP pages

    I have noted in previous articles that Sage CRM 7.2 has eliminated the use of Frames within its general screen architecture. Why Remove the Framesets? The Impact of Frameset Removal on CTI integrations The Impact of Frameset Removal on Code in Upgraded Systems ASP pages however are...