Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.
Browse by Tags
All Tags »
Edit Screen (
RSS)
-
|
This article has been updated to correct links and to bring the code in line with the convention introduced in Sage CRM 6.2. You can render a page using var myBlock = CRM.GetBlock("opportunitylist"...
|
-
|
This article has been updated to ensure the code follows the coding convention introduced in Sage CRM 6.2. The code below demonstrates how a page like the Preferences screen can be rebuilt in Sage CRM...
|
-
|
This article has been updated to correct links and to bring the code into line with the new coding standard introduced with Sage CRM 6.2. I have blogged previously on creating Multi block screens based...
|
-
|
This article has been updated to correct links. 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...
|
-
|
Below is a very simple example of a self service page that allows a case belonging to an authenticated visitor to be edited. The ASP code is found below. The code is marked in different colours and discussed...
|
-
|
I have written before about the creation of a complex screen where the ASP page offers the user the ability to edit two records at the same time. See: http://dpp.sagecrm.com/blogs/hints_tips_and_tricks...
|
-
|
The word Block crops up over 1300 times in the Sage CRM developers guide. The word is actually quite a loose term that is used to name some of the Application Programming Interface (API) objects that can...
|
-
|
We should now consider the creation of an edit screen for a Record using an ASP page. The structure is simpler. var myBlock = eWare.GetBlock('OpportunityDetailBox'); var myRecordId = eWare.GetContextInfo...
|