Default language.

Field name considerations


When the ODBC driver accesses a currency field — for example, when you run a report — it generates four or more column names for the field by adding these suffixes to the field name:

  • _Date
  • _Type
  • _Value
  • _functionalCurrencyCode

The driver creates one column for each functional currency defined for the field.

If the form contains a field with a name that is the same as one of the generated names, the ODBC driver reports "Cannot define field more than once" and fails to get the data.

To prevent this issue, do not use field names that conflict with the column names generated by the ODBC driver for currency fields.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Remedy Action Request System 20.02