View more results: All Community | Partner Community
  • Blog Post: Control of Grids, Lists and Columns Using the Client Side API

    The Client Side API contains methods that make it much easier to select rows, columns and individual cells for manipulation. Properties can be set, new data displayed in tool tips and the style of each cell can be changed. The documentation contains a good discussion of how to use the API. You can...
  • Blog Post: 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: 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...
  • Blog Post: Calling extensions (ASP pages and .NET assemblies) from buttons added using the client side API

    The new Client Side API adds a very easy way of adding new buttons. crm.addButton(imageURL,captionfamily,captioncode,[options]) The new Client Side API allows application extensions to be called. This would typically mean calling either an ASP page or a .NET assembly. In order to do this we need...
  • Blog Post: Controlling the properties of New Buttons adding using the Client Side API

    The previous article " Calling Extensions (ASP pages and .NET assemblies) from Buttons added using the Client Side API " discussed how new buttons can be added to system screens. This article will look at how we can add the button exactly where we need and how we can control the behaviour...
  • Blog Post: Adding a Print Screen button to a system page using the client side API

    In this article I would like to consider 3 examples of adding a custom print button to a system screen. The button to be added will open a new version of the current screen that has minimal formatting which will allow the relevant information on the screen to be printed. The screen that will be used...
  • Blog Post: Adding Protection to Your Code in Script Libraries

    A partner recently asked me "how can I discourage any fiddling with the code I have written for my customer". The person who asked me this was anxious about two things. They wanted to make sure that their code didn't break, and they didn't want unauthorized people to 'borrow'...
  • Blog Post: Controlling FusionChart Widgets with the Client Side API

    The image above shows that the value of the oppo_certainty field has been rendered as a graphic widget. The certainty is shown as a value on a linear gauge using the features of the FusionChart libraries that can be used within Sage CRM. I created the chart above using the following code that was...
  • Blog Post: Adding Additional Information to the TopContent of a System Screen using the Client Side API

    In the image below you can see that I have added some additional HTML to the TopContent of the Person Summary screen. The following code can be added to the custom content box of a system screen like the PersonBoxLong or CompanyBoxLong. [code language="javascript"] <script> crm...
  • Blog Post: Creating a Mashup with a FusionChart and Ajax Data using the Client Side API

    The screen shot above of a Company Summary screen shows a graph displaying the count of opportunities and cases belonging to the company in the TopContent area. This has been created using the following code added to the Custom Content box of the CompanyBoxLong screen. <script> var myResults...
  • Blog Post: Creating a compound filter (filterWhere) using the Client Side API

    This article is about the client side API. Specifically this article is concerned with how to write a script to handle the information within a grid and then apply an action to the cells, row or columns of the grid where more than one criteria is needed. Examples of using the client side API with...
  • Blog Post: Using Client Side code in Workflow

    You can use Client Side code in Sage CRM workflow. The image below shows an Opportunity that is being progressed through a workflow in Sage CRM. In this example opportunity workflow the maximum certainty allowed for any stage has been controlled. e.g. Lead - 5 Qualified - 10 Quote Submitted - 15 Negotiating...
  • Blog Post: Hiding a button on a Dedupe Screen in Sage CRM 2017 R2

    A customer had the following requirement. They wanted to be able to hide the ‘Ignore Warning and Enter Company’ button for all non-administration users when dedupe was turned on and when Sage CRM flags that the user is entering a duplicate company. The customer wants all users without system...
  • Blog Post: Identifying and controlling buttons by image names in the interface.

    The client side API allows us to remove buttons from the screen. <script> crm.ready(function(){ crm.hideButton("executesummaryreport.gif"); }) </script> Note: The 'name' of the button is case sensitive so that 'executesummaryreport.gif' is not the same as 'ExecuteSummaryReport...