Skip to main content

Dynamic mapping task lineage

A dynamic mapping task can contain multiple jobs, each with different source and target configurations. Atlan resolves lineage individually per job—applying job-specific configurations and resolving parameter values independently.

How lineage is resolved​

Atlan determines source and target fields separately, with each following its own resolution logic based on how the job is configured.

Source fields​

Atlan uses its SQL Parser to extract source fields directly from the parameterized query—but only when the query contains explicit field names. For example, a job where Source_Table is set to:

SELECT HOUSE_NUMBER, FAMILY_NAME, ADDRESS, NUMBER_OF_MEMBERS, YEAR FROM ...

The parser extracts each field to build the source field list, then links those fields to the next transformation on a 1-1 name-match basis, mirroring how Informatica CDI executes the mapping at runtime.

ConfigurationDetailSupportedFields derived fromMapping derived from
Parameterized QuerySQL query with explicit fields, for example SELECT col_x FROM tab_1;✅Atlan SQL Parser1-1 name match to next transformation
Parameterized QuerySELECT * FROM tab_1 pattern❌——
Parameterized Single ObjectTable name passed as a parameter❌——

For SELECT * queries and parameterized single objects, both field-level and object-level lineage are missing—Atlan can't derive field details from the Informatica API exports for these configurations.

Target fields​

Target field resolution happens in two steps. The Object Type defines the source of fields—if set to Parameter or Single Object, fields come from the output of the previous transformation. The Field Mapping Type controls how fields are mapped: Completely Parameterized derives both the field list and mapping from the parameter expression, resolving values per job, while Automatic maps fields by matching names from the incoming transformation.

ConfigurationDetailSupportedFields derived fromMapping derived from
Target Object: Parameter / Single ObjectTarget fields inferred from upstream transformation output✅Previous transformationPer the Field Mapping Type setting
Field Mapping Type: AutomaticFields automatically mapped by name from incoming transformation✅1-1 name match1-1 name match on incoming fields
Field Mapping Type: Completely ParameterizedAll target fields defined via parameter expression✅Parameter expressionParameter expression (resolved per job)
Field Mapping Type: Partially Parameterized / ManualMix of parameterized and hand-picked fields, or fully manual mapping❌——

See also​