Rules and Guidelines for Validating Field Mappings
Use the following rules and guidelines when you validate an expression in a field mapping:
- •When you validate mappings, Informatica Cloud performs the following validations:
- - Verifies that the source and target fields in the task exist in the source or target. If the field does not exist, an error appears.
- - Verifies that all column datatypes are string and all field expressions contain string operations when the source and target are flat files.
- - Verifies that the correct parameters are used for each function and that the function is valid.
- •The expression validator does not perform case-sensitive checks on field names.
- •The expression validator verifies that the datatype of a field in an expression matches the datatype expected by the containing function. However, the expression validator does not check for incompatible datatypes between the following sets of objects:
- - Source and target fields of tasks.
- - Source field in a lookup condition and the lookup field.
- - Output of an expression or lookup and the target field.
The expression or lookup with these incompatible datatypes may validate successfully, but, at runtime, the task fails and an error appears.
- •If you map a string source field to a number target field, the validation succeeds. The application tries to convert the string to a number using the atoi (ASCII to Integer) C function.
- •The expression validator does not validate lookups.
- •If you validate the field mapping after you save the task, the following error may appear:
Missing data type on one or more source fields. Please click Refresh Fields button to reload fields.
To resolve this issue, refresh the fields. When you refresh the fields, Informatica Cloud retrieves and updates the latest field attributes, including the field datatypes.