Siebel Developer's Reference > Operators and Expressions > Expressions >

Guidelines for Configuring Calculated Fields

If you configure a calculated field, then use the following guidelines:

• You must not use a calculated field to do an update. A calculated field does not support an update for even a simple expression, such as [Field]). The exception is that a specialized business component can override SqlSetFieldValue. For important caution information, see Using Specialized Classes.
• If the calculated value of a calculated field is not a DTYPE_TEXT value, then you must explicitly specify the field type.
• You must not configure Siebel CRM to store a calculated field in a column.
• You must not create validation criteria on a calculated field. Siebel CRM ignores this criteria.
• Siebel CRM supports a query on a calculated field. The work that Siebel CRM performs if it does a query on a calculated field depends on the functions that it uses in the calculation. If Siebel CRM:
  • Can use the function directly in the WHERE clause in the SQL statement, then it uses the function.
  • Cannot use the function directly in the WHERE clause, then Siebel CRM must examine each record in the business component to identify the records that it displays to the user. This configuration impacts performance. The IIf function and Lookup function are examples of functions that Siebel CRM cannot use in the WHERE clause.
• You must not configure Siebel CRM to sort calculated fields.
• You can configure Oracle's Siebel CRM so that a calculated field references the results of another calculated field in the same business component.
• To place a link in a calculated field, you can use the following HTML tag:

  <a href= ...></a>