Many system entities such as Opportunities, Leads and Cases can be assigned to a Team. Custom Entities can also have Teams assigned to them.
For historic reasons the Team field in the database is called channelid.
user_primarychannelid
oppo_channelid…
I thought I had written about this trick before but it appears not!
A customer needed a technique to allow a chart to be displayed at the top of the company screen. This is a bit like the PipeLineGraphic of the OpportunityList or CaseList system screens…
The requirement to allow the user to fall back to an earlier point in the workflow is usually handled by looping. We can see from the diagram below how a workflow can allow a user to drop back and repeat or cycle through certain workflow states again…
The diagram below contains the objects, methods and properties that are the main ones used in the internal COM API of Sage CRM. These objects can be used in field level scripts; Create and Validate and also in TableLevel scripts and Workflow JScript conditions…
The Values() collection can be used in all serverside scripts to examine the passed in Values from a form.
Create Scripts
Validate Scripts
Tablelevel Scripts
Workflow Scripts
The Values() collection must always have an argument passed to…
I have discussed calling Stored Procedures from within Sage CRM before in the the article " Using the COM CRM.CreateQueryObj() to call a Stored Procedure ". From that article it can be seen that it is possible to call stored procedures where ever a QueryObject…
This example code is provided by a colleague in Switzerland. It provides an alternative way of creating an automatically incrementing field value. The result of the code is to create an incrementing number that includes the current "year" as a prefix…
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'"; strSQL += " INSERT notes"; strSQL += " (note_noteid,note_foreigntableid…
The control of field level security can be found against each field listed under the Field tab in the customization area. Administration | Customization | TableName We know from the documentation that the field security interface provides a simple code…
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 able to access the current user id. In ASP pages…