Secondary entities are technically never in context so the GetContextInfo method doesn't work for these entities. For example if you wanted to get the current address id this would not work: GetContextInfo('address', 'addr_addressid'); However when you go into the edit screen of a...

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 by the opportunitylist system action which is used in a number of contexts My CRM Person Company...

A little while ago I wrote an article called " Adding the Document Drop Plugin into a Custom Page ". That article provided the code to include activex plugin into a custompage to allow upload of documents to the library. The orginal article's code that the company and person records were...

The code in article has been corrected, 7th May 2009. An individual screen within CRM will be produced as a result of a hyperlink that looks like this: http://servername/crm/eware.dll/Do?SID=5351668533575&Act=166&Mode=1&CLk=T&Key0=4&Key4=4&Key27=80&T=New I wrote a little while...

This article has been updated (29th April 2009) to use the coding convention introduced in Sage CRM 6.2 Normally when you enter a SQL Tab condition associated with an option in a Tabgroup you can either work with the current entity in context or the current user in context. But what if you want to control...

This article has been updated (29th April 2009) to correct hyperlink references. In a previous article " Tab SQL Clause " I discussed how it is possible to separate SQL clauses with a " ; " character. So in a Company Tab group the Opportunity tab can be guarded by a SQL clause statement...

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. The starting page is an ASP page in the context of the Opportunity. These buttons will allow...

This article has been updated (29th April 2009) to use the coding convention introduced in Sage CRM 6.2 If you have started to code with Sage CRM you will know that the world is seemingly divided into two, ServerSide and ClientSide. The objects and properties that we can use ServerSide can not be used...

GetContextInfo() is perhaps the most commonly used method within the Sage CRM API. This is both within internal code (Create scripts, Validate scripts etc) and application extensions which maybe either COM ASP or .NET API. GetContextInfo() returns a named field from the given table based on the current...

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 a Case's Summary Screen will look something like this: http://localhost/CRM/eware.dll/Do?SID=198369875659391&Act...