Use the Source Definition object for all source types.
For database and flat file sources, use the Source Qualifier object. For all other source types, use the Application Source Qualifier object.
You can use any target object to represent different target types.
The following objects are not supported at this time:
Unconnected Salesforce lookups
Unconnected stored procedure
Related Salesforce sources
When naming a link, use a name that describes the rules associated with the link. This allows you to understand a data flow without having to read the rules for each link.
Do not create a Mapplet object in the
Cloud Integration Template Designer
. You can use a Mapplet object in a Visio template if you can create the mapplet as part of a PowerCenter task and export the PowerCenter mapping XML to be used as a Visio template.
When you configure a data flow that contains expression macros and template parameters to use the field mapping input control, keep them in different Expression objects. Use one Expression object for the expression macros, and another for the field mapping template parameters.
transformation language to define expressions.
For a Normalizer object, generated key values are reset with each job. For a Sequence Generator object, generated key sequence values are also reset with each job.
When you configure multiple group by ports for an Aggregator object, use a semicolon to separate field names. If you create a template parameter for group by ports, you might add a template parameter description when you upload the Visio template.
You can use connected stored procedures and stored functions in a mapplet or in the data flow. Use the following guidelines when using stored procedure objects:
Define the stored procedure in the Expression Text property by stating the stored procedure name, input fields, and output fields:
<Stored Procedure Name>(<inputfield1 datatype>(<precision>,<scale>) IN <inputfield1>, <inputfield2 datatype>(<precision>,<scale>) IN <inputfield2>... <outputfield1 datatype>(<precision>,<scale>) OUT <outputfield1>, <outputfield1 datatype>(<precision>,<scale>) OUT <outputfield2>...)
Match the order of the fields with the order of the template parameters defined in the stored procedure.
Connect all fields in a stored procedure object.
When a stored procedure is used in the data flow, you can parameterize the expression text to reuse same template with different stored procedures. In this case, the input and output link rules for the stored procedure object also needs to be parameterized and link rules mapping should maintain the order of the stored procedure template parameters.
To use a stored function, enter the following syntax in the Expression Text property:
<return value datatype>(<precision>,<scale>)<Stored Function Name>(<inputfield1 datatype>(<precision>,<scale>) IN <inputfield1>, <inputfield2 datatype>(<precision>,<scale>) IN <inputfield2>... <outputfield1 datatype>(<precision>,<scale>) OUT <outputfield1>, <outputfield1 datatype>(<precision>,<scale>) OUT <outputfield2>...)
If issues with string datatypes occur, use the NSTRING datatype for string values.
The field mapping input control appends "_OUT" to the field mapping output field names. When you plan to use a field mapping input control for a template parameter, use a link rule to move output fields with the _OUT suffix to the next object in the data flow.
When you plan to use a field mapping input control to write data to multiple targets with matching field names and matching datatypes, precision, and scale, connecting one field in one target results in writing data to matching fields in both targets. If the target fields have the same name, but different datatypes, precision, or scale, you can map one of the target fields.
Avoid using Mapplet objects or multiple targets to a data flow after a field mapping input control.
When you use multiple instances of the same source object, use a unique table name for each instance of the source. Similarly, when you use more than one instance of a target object, use a unique table name for each instance of the target. And when you use more than one instance of a lookup, use a unique table name for each instance of the lookup.
You can use the %ALL% expression macro in an expression to represent all field names in a transformation. For more information, see "Using the %ALL% Keyword in an Expression" in the
Informatica PowerCenter Mapping Architect for Visio Guide
Use an Update Strategy object only when the target table has keys defined.
In Custom Transformation objects, do not configure a field as both an input and output field and do not include all input fields in the OUTPUT group.
To include the fields from a Custom Transformation in field mappings, set the Fixed Ports property to YES.