View more results: All Community | Partner Community
  • 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 But not all system...
  • Blog Post: Adding Custom Actions to Find Screens

    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 example you may have a requirement to add a new call...
  • Blog Post: Adding a Hot Key keystroke to a Custom Button (added using Button Groups)

    Sage CRM uses Hot Keys to allow users to access some screen actions using Key Strokes rather than just using the mouse. This has been discussed before in the article " Get to your data quicker using shortcuts ". We can add new custom action buttons to screens like the Company Summary screen...
  • Blog Post: More about Using CRM security in ASP pages

    I have previously discussed that access to buttons can be controlled by the 4 & 5 parameter of the CRM.Button() method used in Classic ASP. The entity referenced in the 4th param has to be an entity normally covered by security. The example covered in the previous example discusses whether or...
  • Blog Post: Some thoughts on Sage CRM, FOP, PDF and Reports

    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 not tied to outputting in a particular format, although its usage...
  • 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: Action buttons on Custom Entity Find Screens

    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 is very nearly yes. In the code for a Project Find screen that I have presented here you should be able to see some of the items...
  • 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

    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. (This can also be a custom top level entity) The 5th parameter can be INSERT VIEW EDIT DELETE var strNewCompanySecurityButton...
  • 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

    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 allow me to jump to different places in the application. The first "company" button jump is built using var strCompanyButton = CRM...
  • Blog Post: 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 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

    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"); var myRecord = CRM.FindRecord("opportunity","oppo_opportunityid...
  • 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: 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: 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: Guarding Access to Buttons Built in ASP Pages

    Imagine that you have created a new page that lists data from either Sage CRM or an external system. It maybe that you have classified your users into two types. The first can only view the data, so the actions buttons should be hidden, but the second user type should be able to access the buttons and...
  • Blog Post: Choices in Customizing Lists

    You only need to follow the tags " List Page " or " List Block " to see that there have been lots of articles written already about how lists can be customized. In this article I want to step back and bring all these points together so we can see the range of options that we have...
  • 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...