Repository Guide

Back Next

Rules and Guidelines for Object Compatibility

The Repository Service treats modified dependent objects as compatible when you perform the following tasks:

Change datatypes in a source, target, or transformation to a compatible datatype. The Repository Service marks objects as impacted only when you change the datatypes to incompatible datatypes.

Rename ports in a reusable transformation.

Add a port in a source, target, or transformation.

Replace objects such as sources, targets, mapplets, and mappings with compatible objects.

When you replace a repository object with another object, the following conditions must be true for the Repository Service to treat the objects as compatible:

Repository Object	Compatibility Requirements
Source, Target, Transformation	Name of the replacement object must match the original object. All port names in the original object must be represented in the replacement object. Datatypes must be compatible.
Mapping	Name and number of the following objects must match the original object: Targets Mapplets Sources Source Qualifiers Joiner transformations Update Strategy transformations Custom transformations
Mapplet	Name and number of the following objects must match the original object: Sources Source Qualifiers Joiner transformations Update Strategy transformations Custom transformations

Rename Saved Search

Table of Contents

Repository Guide

Repository Guide

Rules and Guidelines for Object Compatibility

Rules and Guidelines for Object Compatibility