Browse By Tags

  • 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: 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: 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...
  • Blog Post: Using AJAX to access server-side objects client-side (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. *** See my recent blog post for information about an AJAX gotchya *** *** See my recent blog post for a different...
  • 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: Sage CRM 7.2: Script Libraries: Defining Namespace References

    In a previous article " Script Libraries: Reusing Client Side Code Between Screens " I discussed how Sage CRM 7.2 will automatically add any javascript file that you add to the custom folder into the header of every page produced by the system. It is a good idea when adding script libraries...
  • Blog Post: Sage CRM 7.2: Binding Client Side Script to the onLoad event using crm.ready()

    Sage CRM 7.2 has a Client Side method crm.ready() which is used to execute scripts once the page is loaded. In earlier versions of Sage CRM we could use 'Plain Old Javascript' to associate custom code to the moment the page was loaded. In Internet Explorer the way to do this was: window...
  • Blog Post: Sage CRM 7.2: Script Libraries: Reusing Client Side Code Between Screens

    It has always been possible in Sage CRM to share client side code between screens. In Sage CRM v7.1sp2 and earlier we could do this by using a shared external script library. For example if we wanted a set of business rules to be available in both the PersonBoxLong screen and the PersonBoxDedupe screen...
  • 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...
  • Blog Post: Sage CRM 7.2: Controlling the RecentList using Client Side Code

    I have previously written about how the RecentList can be controlled in Client Side script using a technique suitable for Sage CRM v7.1 and earlier. You can find this article here: Clearing the Recent List using Custom Clientside Code (for Sage CRM v7.1 and earlier) The removal of frames in Sage CRM...
  • Blog Post: Gotchya when using AJAX in CRM Customisations (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. Previously I blogged about using AJAX in CRM Customisations. I found a bit of a gotchya that can cause data-loss. Please...
  • Blog Post: Changing Search Select Advanced display fields

    CRM allows you to change the display fields used in an Search Select Advanced (SSA) field but it does not give you control over the order of the fields displayed. The following function, placed in the custom content of the screen, will allow you to change the order of the display fields: <script>...
  • Blog Post: Sage CRM 7.2: Making sure upgraded ASP pages work correctly.

    This article has been prompted by a customer who was left scratching their head when an ASP page that had been working in old install of Sage CRM didn't seem to be 'quite right' in Sage CRM 7.2. The upgraded page seemed to being missing some features when they looked at it after they had...
  • Blog Post: Getting scripts into hard-to-reach places (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. *** Please note that this article describes a technique that exploits undocumented workings of the product. Please read...
  • Blog Post: Sage CRM 7.2: The Evolution of Client Side Code

    Sage CRM supports multiple browsers, Chrome, Firefox, Safari and right from the earliest versions it has supported Internet Explorer. Multi-browser support was added in Sage CRM v7.1sp2. Much of the support for different browsers within the code included in the system screens was made easier by the use...
  • Blog Post: Making Server-side data available through Button URL (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. This article has been updated (29th April 2009) to correct hyperlink references and to use the coding convention introduced...
  • Blog Post: Sage CRM 7.2: Using the Clientside API to control Tabs

    Consider the following business rule. "A customer has a requirement that the Case Tab in the company screen should only display when the Company has an agreed service level agreement and the user accessing the screen is in the 'Customer Service' team." This is a business rule...
  • Blog Post: Accessing documentation & help for the client side API for Sage CRM 7.2

    Sage CRM 7.2 introduced a new powerful and simple to use API for carrying out client side customizations. I have written about the new API in several articles already. You can read a simple overview of the API in the article " The new client side API ". The API has been fully documented...
  • Blog Post: Sage CRM 7.2: Detecting Screen Mode in the Client Side API

    Sage CRM Screens can exist in different ‘Modes’. The basic two modes that we have to worry about in Client Side code are View and Edit. We can use the fact that in Sage CRM 7.2 and earlier <INPUT> HTML tags are named and have an ID with same name as the physical field in the database...
  • Blog Post: Sage CRM 7.2: Control of Grids, Lists and Columns Using the Client Side API

    Below is a screen that shows the highlighting of columns and individual cells in a Grid in an earlier version of Sage CRM. Working with Lists in versions before Sage CRM 7.2 used to be something of a challenge for anyone not very familiar with JavaScript, as can be seen from the article "...
  • Blog Post: Sage CRM 7.2: Creating Ajax calls using the Client Side API.

    Below is a screen shot of an Opportunity Summary page. You can see that as the mouse hovered over the Company Name in the 'For' panel of the screen a tool-tip appeared that displayed the company's Status and Type. This is information that is not normally available within the browser when...
  • Blog Post: Sage CRM 7.2: Controlling Tabs with the Client Side API

    One of the common requirements that I hear during my conversations with partners and customers who are implementing Sage CRM is that at different points within a workflow or business process the organisation may need to make a user concentrate on only certain options that are most relevant at the time...