Once you have been working with Sage CRM for a little while you will notice that the primary keys (unique ID fields) have been suppressed from the interface. By that, I mean that you can't refer to them directly in Lists and Screens.
This is normally…
Imagine you have a requirement to a ensure that a particular opportunity field contains certain data as an Opportunity record is inserted. In addition this information should be partially derived from the parent company data. For example the oppo_customerref…
Entities such as Case and Solution use a reference field as an alternative key. This is the 'ticket' number (case_referenceid, soln_referenceid) that is used as a public and convienent way of identifying each record.
In the default demo system the fields…
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…
In the default system the StoredProc datatype is used to generate the reference id values for
Case_referenceid
Soln_referenceid
When a new record is created, these columns invoke a call to the a Stored procedure called: eware_default_values.…
The StoredProc data type only will fire when a record object is added to a screen object. Specifically this must be a new record. The actually firing of the StoredProc is tied to the loading of the interface rather than the use of the record object. When…
Is there a way to set the case ref id using the eware_default_values procedure based on the case type?
we have a field case_c_type, which is pre-filled by the workflow when the case is created to either 'CSI' or 'NCN' dependng on the workflow used.…