View more results: All Community | Partner Community
  • Blog Post: Working with 'Create Follow-Up Task' and 'Create Follow-Up Appointments' using Server Side code

    The image above shows the New Task screen. Both the New Task and New Appointment screens allow a user to Create Follow-up Communications. A customer might have a business requirement to know whether the communication a user is currently entering is actually a followup of another communication. That...
  • Blog Post: Logging on to Sage CRM from within an Intranet Page

    Some time ago I was asked about how users of an company intranet could have a logon screen presented to them that was part of an existing intranet page that when completed would bring the user into Sage CRM. In addition, once the user had finished their work inside Sage CRM and logged out they should...
  • Blog Post: An Example of Codeless Customization: Adding Extra User Record fields to the interface

    This article is based on a requirement that a customer had to store additional information about each user that was also under the control of the user. The original customer requirement was quite simple, they needed to allow each user to maintain their own home address, date of birth and next of kin...
  • 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: Building a Workflow Map Diagram that Shows Progress through Workflow

    Workflows in Sage CRM can become long and a user may wish they had a version of the diagram that is available when the workflow is constructed. You can see from this image below that an extra button has been added to the Opportunity screen. In this example application, when the 'Workflow Map'...
  • Blog Post: Who's been looking at my data? Recording access to Company and Person screens

    I have discussed creating logs and audit trails of changes to data in previous articles. See Using a Table Level Script to Track Changes to Data Made by Users. Validation rules don't always mean "Stop!" But many customers have the much more straight forward business need...
  • 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: Adding Buttons and Customizing the Email Screens

    Sometimes, just sometimes, I am left scratching my head about how to do something in Sage CRM. And then with a little more thinking, and exploration of the product and reading of the documentation I find that it is easier than I expected. An example of this was tracking down how to add Buttons to...
  • 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: Calling CRM Actions

    The CRM.URL() method is used to allow you to build correctly formatted URLs that reach back into the application. Most commonly this is used to interact with ASP pages and with Sage CRM .NET application extensions. For example to build a button that calls an ASP page the code would look like: var...
  • 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: How to Hide the Assigned User Column in the Case List when in My CRM context

    A customer had the requirement to hide the column "Assigned To" from the Case List in the MyCRM menu. but show it in other contexts like company, person and especially Team? Note : This would be the same idea for any List called from the My CRM or Team contexts, e.g OpportunityList...
  • Blog Post: Changing the Default Screen Displayed when Accessing a Record from the RecentList (Sage CRM v7.1)

    A customer had the requirement that when a Person was selected from the Sage CRM RecentList, as in the image below, the NotesList associated should be displayed rather than the Person Summary screen. When the Person is selected from the RecentList The Notes tab is displayed. This is not...
  • Blog Post: Passing Parameters and Automatic Logons

    Some time ago I wrote an article " Passing Parameters Directly to CRM on Startup ". The example I gave in that post was a URL that could be sent to someone in an email. The URL hyperlink when followed would prompt the user for a log in and then take them to the standard opportunity list. http...
  • Blog Post: How does metadata create a Screen?

    If we consider a screen like the Case Summary screen we can imagine it being built in a series of layers. If we consider the hyperlink http://localhost/CRM/eware.dll/Do?SID=198369875659391&Act=281&Mode=1&CLk=T&Key0=8&Key1=43&Key2=57&Key8=46&T=Case We can see that the Action...
  • 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: Is this the final word on what the URL variables mean?

    A screen is called as a result of a hyperlink. This may be a button click, a call from the recent list or any other selection from the interface. A URL of a Case's Summary Screen will look something like this: http://localhost/CRM/eware.dll/Do?SID=198369875659391&Act=281&Mode=1&CLk...
  • Blog Post: Listing System Actions

    System Actions are not formally part of the official API and there is no list of them in the documentation although there are plenty of articles that make use of them. The article "Calling CRM Actions" is a good introduction to how the inbuilt System Actions can be referenced in custom pages...
  • 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: Oh botherations! Shoot, drat and darn!

    It just goes to show that this blog describes tips that could just as well be described as 'traps'. Like most of you I try and use tricks that sometimes inhabit the grey zone between what is possible and what shouldn't be done. The interface has several features that allow us ride on existing...
  • 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: 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: The Forward and Back buttons (Page History) in code

    Creating your own forward and backwards buttons You can create buttons that make use of the internal system actions that control the forward and backward behaviour. var strForwardButton = CRM.Button("Forward","forward.gif",CRM.URL(522)); var strBackButton = CRM.Button("Back"...
  • Blog Post: Customizing a Screen

    A screen is called as a result of a hyperlink. This may be a button click, a call from the recent list or any other selection from the interface. A URL of a Case's Summary Screen will look something like this: http://localhost/CRM/eware.dll/Do?SID=198369875659391&Act=281&Mode=1&CLk...