When you write expressions that use in-out parameters, you don't need string identifiers for string variables.

When you use a parameter in a transformation, enclose string parameters in string identifiers, such as single quotation marks, to indicate the parameter is a string.

When you use in-out parameter in a source filter of type date/time, you must enclose the in-out parameter in single quotes because the value received after

Informatica Intelligent Cloud Services

resolves the in-out parameter can contain spaces.

When you use an in-out parameter as a source query, the parameter must contain a valid query as the default value.

If you copy

, import, or export

a

mapping

task, the session values of the in-out parameters are included.

You can't use in-out parameters in a link rule or as part of a field name in a mapping.

An in-out parameter name can't be the same as a field name or part of a field name.

You can't use in-out parameters in an expression macro, because they rely on column names.

When you use an in-out parameter in an expression or parameter file, precede the parameter name with two dollar signs ($$).

For some connection types, when you use an in-out parameter for a date/time value, you cannot use $$$SESSSTARTTIME to override the parameter value in a parameter file.

An in-out parameter value can't exceed 4000 characters.

A

mapping

task can't resolve a nested in-out parameter when the following conditions are true:

A parameter file updates an in-out parameter value in a mapping in advanced mode.
The parameter value is an expression that contains another in-out parameter.

You can't preview data for sources and transformations with in-out parameters that are in mappings in advanced mode.