## What does Atlan crawl from Informatica CDI

URL: https://docs.atlan.com/apps/connectors/etl-tools/informatica-cdi/references/what-does-atlan-crawl-from-informatica-cdi

> During an Informatica Cloud Data Integration crawl, Atlan extracts metadata for Projects, Folders, Mapping Tasks, Mappings, Transformations, and Transformation Fields. Reference tables map each Informatica CDI property to its Atlan asset.

Atlan extracts metadata for Projects, Folders, Mapping Tasks, Mappings, Transformations, and Transformation Fields from Informatica Cloud Data Integration and maps each property to its internal asset model. The tables below list which Informatica CDI properties are read and how they appear on the corresponding Atlan asset.

:::info Important!
The Informatica GUID (source system global unique identifier) for an object is available as part of the Atlan object Qualified Name (QN) and additionally in the `flowId` attribute (for SDK based consumption).
:::

## Project

| Source property | Atlan property | Where in Atlan |
|-----------------|----------------|----------------|
| name | name | name |
| description | description | description |
| updatedTime | sourceUpdatedAt | Last updated (on Informatica CDI) |
| updatedBy | sourceUpdatedBy | Last updated (on Informatica CDI) by |

## Folder

| Source property | Atlan property | Where in Atlan |
|-----------------|----------------|----------------|
| name | name | name |
| description | description | description |
| updatedTime | sourceUpdatedAt | Last updated (on Informatica CDI) |
| updatedBy | sourceUpdatedBy | Last updated (on Informatica CDI) by |

## Mapping task

| Source property | Where in Atlan| Atlan property |
|-----------------|----------|----------------|
| Task Name | name | name |
| Description | description | description |
| Location | flowProjectName, flowFolderName | Project, Folder |

Atlan also supports [Mapping Task (Advanced)](https://docs.informatica.com/integration-cloud/data-integration/current-version/mappings/mappings/mappings-in-advanced-mode.html) and [Dynamic Mapping Tasks](https://docs.informatica.com/integration-cloud/cloud-data-integration/current-version/tasks/dynamic-mapping-tasks.html). A dynamic mapping task can contain multiple jobs with different source and target configurations—Atlan captures lineage individually for every job. See [Dynamic mapping task lineage](https://docs.atlan.com/llms/connectors/informatica-cdi/dynamic-mapping-task-lineage/llms.txt) for details on supported scenarios.

## Mapping

| Source property | Where in Atlan| Atlan property |
|-----------------|----------|----------------|
| name | name | name |
| Location | flowProjectName, flowFolderName | Project, Folder |
| Number of transformations in the mapping | flowDatasetCount | |

## Transformation

| Source property | Where in Atlan| Atlan property |
|-----------------|----------|----------------|
| Name | name | name |
| Description | description | description |
| Type | flowType | transformationType |
| Number of fields in the transformation | flowFieldCount | |

## Transformation field

| Source property | Where in Atlan| Atlan property |
|-----------------|----------|----------------|
| Name | name | name |
| Type | flowDataType | Field Type |

---