Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.
Browse by Tags
All Tags »
create script »
ASP (
RSS)
-
|
This article has been edited (1st November 2009) to correct links and make the code follow the convention introduced in Sage CRM 6.2 The requirement to allow the user to fall back to an earlier point in...
|
-
|
In the image below we can see the Company Name is displayed in an opportunity list that is in the context of the company and so that column is redundant and does not need to be shown. The list is created...
|
-
|
This technique covers the use of the Document Drop ActiveX plugin within a custompage. The Document Drop Plugin is used within Sage CRM to allow the easy upload of documents to the library and will also...
|
-
|
Below is some code that illustrates how a Stored Procedure maybe invoked in the QueryObject. var strSQL = "DECLARE @@ret int"; strSQL += " EXEC @@ret=eware_get_identity_id 'notes'";...
|
-
|
Please note there has been a coding standard change between Sage CRM 6.1 and Sage CRM 6.2. The instantiated COM object in Sage CRM 6.2 now has an alias of "CRM" rather that "eWare"...
|
-
|
Above is a screen shot that shows a default opportunity summary page. At the top of the page is the frame that contains the TopContent information. Sometimes this is called the context information. In...
|
-
|
If you need to control the display of screen elements like buttons in ASP pages (or even client side in the browser screens) according to the identity of the CRM users then you will obviously need to be...
|
-
|
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...
|
-
|
How do I tell inside a server side script (or ASP Page) whether or not the script is executing within a SOLO client? This is an important question as if you need to execute SQL against the database e.g...
|