Visit Sage CRM Main Website
About Sage CRM
Browse By Tags
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...
31 Oct 2009
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...
10 Feb 2009
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...
21 Jan 2008
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...
10 Nov 2008
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...
7 Mar 2011
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...
1 Apr 2008
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...
10 Feb 2009
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"...
16 Sep 2011
New Company and New Person buttons in a Custom Entity screen.
A customer had a requirement for a summary screen for a custom entity to provide a new company and new person button similar to the core system entities within Sage CRM. I have assumed that the custom entity pages have been built using the classic ASP pages rather than the .NET API. The example I...
21 Sep 2015
© The Sage Group plc 2019
All Rights Reserved