When you use a dynamic lookup cache in a mapping or mapplet, you can configure a lookup
condition that includes all the lookup fields.
Previously, if the lookup condition contained all the lookup fields, the mapping or mapplet
was invalid because lookup fields used in the lookup condition are ignored in the comparison
with a dynamic lookup cache.
Mappings in SQL ELT mode
Mappings in SQL ELT mode have the following behavior changes:
Field metadata for sources, targets, and lookups
By default, the Source, Target, and Lookup transformations in a mapping in SQL ELT
mode display the native data type, precision, and scale for all fields on the
Fields
tab. You can optionally display the Informatica
transformation data type, precision, and scale.
Previously, by default, these transformations displayed the transformation data type,
precision, and scale on the
Fields
tab.
Lookups against a target
In mappings in SQL ELT mode, you can configure a Lookup transformation to perform a
lookup against a source or target. You can’t create a connection or connection
parameter directly in a Lookup transformation.
Previously, you could configure a Lookup transformation in a mapping in SQL ELT mode
to perform a lookup against a source but not a target.
For more information about mappings in SQL ELT mode, see
Mappings
.
Naming conventions
You can use a double underscore when naming the following assets and objects:
Connections
Mappings
Mapplets
Sessions
Taskflows
Transformations
Workflows
Additionally, the following assets
, fields, source
objects, and target
objects can now have names of up to 255 characters:
ASK INFAPreview
