Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.
Browse by Tags
All Tags »
buttons (
RSS)
-
|
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/...
|
-
|
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...
|
-
|
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...
|
-
|
This article shows how to add a button to an existing system screen that will call a report. For example if you look at the image of the OpportunitiesList screen below you can see that a button has been...
|
-
|
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...
|
-
|
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...
|
-
|
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...
|
-
|
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...
|
-
|
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...
|
-
|
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"...
|
-
|
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...
|
-
|
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...
|
-
|
This has article has been corrected! Please note in the code below jxxxscript should read javascript. I have written before about building buttons that call the inbuilt system actions. The action code...
|
-
|
This is a trick that applies to Sage CRM 6.1 (and earlier). Sage CRM 6.1 added the capability to add new Buttons to screens generated from system actions such as the RelatedCompaniesList. This uses the...
|
-
|
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...
|
More Posts
Next page »