• 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 Extra Buttons to the Saved Search Screen

    Sage CRM has a feature called Button Groups that allow a system administrator to add buttons to System Screens. I have discussed Button Groups in several articles. Adding Buttons and Customizing the Email Screens Adding Buttons and Customizing the Outbound Call Screens Adding a Print Button...
  • Blog Post: Adding Custom Actions to Find Screens

    This article has been updated to correct links. There is a previous article, " Action buttons on Custom Entity Find Screens " This post explained how to recreate a find screen but I am now going to consider adding a new Action button to an existing system find screen. (See below) For...
  • Blog Post: Controlling Button Positions in ASP pages

    A customer had a requirement to add additional buttons to a custom ASP page. These buttons had to be displayed at the bottom of the screen in a way similar to the buttons in the marketing area. But you can have the buttons appear anywhere you like in an ASP (or .NET) page. If you have only one...
  • 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: Creating Communications Using Actions

    This article has been updated (7th July 2009) to use the coding convetion introduced in Sage CRM 6.2 and also to provide an additional tip for when creating communications using system actions. It is possible to create buttons on ASP pages that call in built behaviour. var CustomButton = CRM.Button...
  • Blog Post: Customizing Help Buttons

    This article discusses how a system administrator can link the help button within a system screen to a new or revised help file. Throughout Sage CRM the system generated pages have help buttons which link to contextual help. If you are on the Company Search screen and you click the help button then...
  • Blog Post: Action buttons on Custom Entity Find Screens

    The code in this article has been updated (31st October 2009) to follow the coding convention introduced with Sage CRM 6.2 Below is a picture of the Company Find screen.. This is the standard system screen. But can this screen be duplicated for new entities such as "Project". The answer...
  • Blog Post: Using Tabgroups to define Action Buttons in COM API ASP

    The code in this article has been updated (31st October 2009) to follow the convention introduced in Sage CRM. If you have the Extensibility license, you can create new tab groups and you can perform Advanced Tab Customization. In ASP pages using the COM API we can call custom tab groups by using...
  • Blog Post: How did I get Here?

    In this post I would like to consider how you can establish whether a page has just been called via a hyperlink (from the tab) or it has been called because "Save" action button has been pressed. Pages can be called either by direct hyperlinking to them or by clicking a "button"....
  • Blog Post: Using CRM security in ASP pages

    This article has been updated to bring the sample code into line with the new standard introduced with Sage CRM 6.2. Access to buttons can be controlled by the 4 & 5 parameter of the CRM.Button() method. The entity referenced in the 4th param has to be an entity normally covered by security...
  • Blog Post: Adding Extra Buttons to the Group Details Screen

    I have written another article that discusses how to add an extra button to the Saved Search Screen . That article discussed how most system screens can have additional action buttons added to them using the Buttons Group feature. But two important exceptions are the Saved Search screen and the Group...
  • Blog Post: How Sage CRM Hot Keys work

    Previous articles have discussed how Hot Keys can be added into Sage CRM. Get to your data quicker using shortcuts Adding a Hot Key keystroke to a Custom Button (added using Button Groups) What these articles have not explained is how the Hot Keys are implemented as code within the Sage...
  • Blog Post: More thoughts on adding Action buttons to Find Screens

    SyntaxHighlighter.config.clipboardSwf = '/dp.SyntaxHighlighter/Scripts/clipboard.swf'; SyntaxHighlighter.all(); I wrote an article previously that showed how the action buttons on the system search screens set a hidden value in the form. This is the "TargetAction" field. For example...
  • Blog Post: Changing Context when jumping between pages using the COM ASP API

    This article has been updated (29th April 2009) to correct hyperlink references and to use the coding convention introduced in Sage CRM 6.2 I have created a very simple page that contains a couple of buttons. The starting page is an ASP page in the context of the Opportunity. These buttons will...
  • Blog Post: Sage CRM v7.1 SP2: Hot Keys in Different Browsers

    The article " How Sage CRM Hot Keys work " explained how Hot Keys are implemented using the hyperlink AccessKey property in a browser. That article explained how the Case Summary screen has a series of Hot Keys associated with the different actions buttons on the screen. These were implemented...
  • Blog Post: Custom Buttons in Self Service

    If you are working with Self Service and tried to build a custom button using the techniques discussed in the article " Adding Buttons to an ASP Page ". e.g. var strCallASPButton = CRM.Button("ASP","save.gif", CRM.Url("myPage.asp")); myBlock.AddButton(strCallASPButton...
  • Blog Post: How to launch a Crystal Report from a Custom ASP page.

    To create a button that calls a hyperlink that is properly formed and uses the correct SessionID information you can use the eWare.URL method. //myBlock is a screen, list or container block var strFindCompanyButton = eWare.Button("search","search.gif", eWare.Url(130)); myBlock...
  • Blog Post: How to Build Buttons that call the Email Editor using the COM ASP API

    This has article has been corrected and the code reformatted 17th October 2011. I have written before about building buttons that call the inbuilt system actions. The action code for the internal email editor is 1500. We can set up a new SendEmail button on a custom page that will either display...
  • Blog Post: Adding Buttons to an ASP Page

    This article has been updated to follow the Sage CRM 6.2 coding standard. Consider the code below. This is for a simple edit screen for the Opportunity entity. var intRecordId = CRM.GetContextInfo("opportunity","oppo_opportunityid"); var myBlock = CRM.GetBlock("opportunitydetailbox"...
  • Blog Post: Controlling Buttons in Self Service

    Self Service in Sage CRM v7.1 and earlier uses the COM API. Much of the use of the API in Self Service is very similar to the creation of ASP pages as extensions to the main user interface. I have noted in previous articles the Self Service API is actually a separate API and the usage of the blocks...
  • Blog Post: More about Using CRM security in ASP pages

    This article has been updated to bring the code into line with the coding standard introduced in Sage CRM 6.2. I have previously discussed that access to buttons can be controlled by the 4 & 5 parameter of the eWare.Button() method. The entity referenced in the 4th param has to be an entity...
  • Blog Post: Some thoughts on Sage CRM, FOP, PDF and Reports

    This article has been edited (31st October 2009) to correct links. Sage CRM uses Apache FOP (Formatting Objects Processor) to generate its reports in PDF format. See http://xmlgraphics.apache.org/fop/ FOP is an example of a print formatter that uses XSL formatting objects (XSL-FO) and is in theory...
  • Blog Post: Adding a Button that Passes Contextual Information to an External Webpage

    You can add a button In a custom ASP page In a the code of a .NET assembly In a an existing system screen Buttons in an ASP Page If this is in an ASP page then the code for a simple button to call an external ASP page looks like var strCallASPButton = CRM.Button("ASP"...
  • Blog Post: Hiding Buttons using Client Side Code

    The idea of hiding buttons has been discussed before on the blog as can be seen from this post: Controlling Buttons using Client Side code Recently there has been an exchange of emails within an internal Sage mail-group which has come up with some very good techniques. The material below has come from...