Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

JDBC V2 Connector

JDBC V2 Connector

Rules and guidelines for migrating a mapping

Rules and guidelines for migrating a mapping

Consider the following rules and guidelines when you use the same or a different object path for the migrated mapping:
  • The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:
    Transformations
    Object Type
    Advanced Fields
    Source
    Single object
    Schema and table name
    Lookup
    Single object
    Applicable for unconnected and connected, cached and uncached.
    Target
    Single object
  • You can't dynamically refresh the data object schema at run time. You need to maintain the same metadata for the table selected in the Source, Target, or Lookup transformation and the corresponding advanced field overrides, as schema change handling is not applicable.
  • You can't migrate a mapping that uses the Hosted Agent as the runtime environment.
  • If the mapping contains an advanced filter for the object in the
    Query Options
    section and an override of the object in the advanced properties, you need to use the object specified as an override in the advanced properties to define the condition.
  • If the mapping contains multiple objects, you can't override the schema and table name from the advanced properties.

0 COMMENTS

We’d like to hear from you!