Product Information

Product: Centerprise Integration Studio
Version: 2.0
Operating System: Windows XP Professional

Document Details

Symptoms:

When using the expression builder, you may receive one of several error messages while compiling an expression:

• Unexpected token ")",expected";', on line:1 column 22.
• Error: Invalid identifier <IF>.
• Error: Invalid identifier <Objectname>.
• Type mismatch for operator <=>. Boolean = Int64 is not allowed.
• The rule does not evaluate to a compatible data type.

Resolution:

Expressions may not compile for several reasons:

1. Unexpected token ")",expected";', on line:1 column 22. This means the syntax is incorrect and the error lies on line 1, column 22. The cause of error may be an incorrect, extra or missing symbol in the rule. To fix the issue, locate the error and modify the rule accordingly.
   
2. Error: Invalid identifier <IF>. This "invalid identifier" error message informs you that the syntax used is in upper case and is therefore invalid. Other such invalid identifiers are 'AND' and 'OR'. To fix the error, change the identifier to lower case.
   
3. Error: Invalid identifier <Objectname>. This "invalid identifier" error message notifies you that the object or field name used in the rule is invalid. This could either mean that it does not exist in the table, or it contains a spelling error. To fix this error, ensure that the object or field name in the rule matches with the Business Objects listed in the Expression Builder dialog box.
   
4. Type mismatch for operator <=>. Boolean = Int64 is not allowed. This error message means that the operator used in the formula: "=" is not valid because the object preceding it is a boolean data type, while the value succeeding it is an integer. To fix this error, change the operator or the value succeeding the operator. In this case, you could change the value to a boolean data type.
   
5. The rule does not evaluate to a compatible data type. This error message, like the one above, means that the rule written evaluates to a different data type from what is expected by the application. To fix this error, rewrite the rule so that it evaluates to the correct data type.
   

For more information on rules and the data types expected, refer to the functions glossary.