What does Atlan crawl from Amazon QuickSight?
Atlan currently supports lineage for the Amazon QuickSight connector to the following data sources:.
Atlan currently supports lineage for the Amazon QuickSight connector to the following data sources:
Atlan crawls and maps the following assets and properties from Amazon QuickSight.
Analyses
Atlan maps analyses from Amazon QuickSight to its QuickSightAnalysis asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| status | quickSightAnalysisStatus |
| calculatedFields | quickSightAnalysisCalculatedFields |
| parameterDeclarations | quickSightAnalysisParameterDeclarations |
| filterGroups | quickSightAnalysisFilterGroups |
Dashboards
Atlan maps dashboards from Amazon QuickSight to its QuickSightDashboard asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| publishedVersionNumber | quickSightDashboardPublishedVersionNumber |
| lastPublishedTime | quickSightDashboardLastPublishedTime |
| analysisName | quickSightAnalysisQualifiedName |
Datasets
Atlan maps datasets from Amazon QuickSight to its QuickSightDataset asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| ImportMode | quickSightDatasetImportMode |
| outputColumnCount | quickSightDatasetColumnCount |
Folders
Atlan maps folders from Amazon QuickSight to its QuickSightFolder asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| FolderType | quickSightFolderType |
| SharingModel | quickSightFolderSharingModel |
| folderHierarchy | quickSightFolderHierarchy |
Dataset fields
Atlan maps dataset fields from Amazon QuickSight to its QuickSightDatasetField asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| type | quickSightDatasetFieldType |
| datasetQualifiedName | quickSightDatasetQualifiedName |
Analysis visuals
Atlan maps analysis visuals from Amazon QuickSight to its QuickSightAnalysisVisual asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| Id | quickSightId |
| analysisQualifiedName | quickSightAnalysisQualifiedName |
| sheetId | quickSightSheetId |
| sheetName | quickSightSheetName |
Dashboard visuals
Atlan maps dashboard visuals from Amazon QuickSight to its QuickSightDashboardVisual asset type.
| Source property | Atlan property |
|---|---|
| name | name |
| createdAt | sourceCreatedAt |
| updatedAt | sourceUpdatedAt |
| Id | quickSightId |
| dashboardQualifiedName | quickSightDashboardQualifiedName |
| sheetId | quickSightSheetId |
| sheetName | quickSightSheetName |
Analysis fields
Atlan maps each field a visual consumes inside an analysis to its QuickSightAnalysisField asset type. This covers both dataset fields referenced directly by a visual and calculated fields used in that visual. Each analysis field is scoped to the visual that consumes it and becomes a child of the corresponding QuickSightAnalysisVisual, so the same field used in two visuals produces two separate assets.
| Source property | Atlan property |
|---|---|
| Name | name |
| Expression | quickSightAnalysisFieldExpression |
| DataSetIdentifier | quickSightAnalysisFieldDataSetIdentifier |
| Parent visual | quickSightAnalysisVisual |
quickSightAnalysisFieldExpression is populated only for calculated fields. A field's identity is scoped to its analysis, sheet, visual, and dataset, so the same field name can appear as separate assets across different visuals or datasets without colliding.
How field-level lineage works
Atlan models field-level lineage for analyses as field-to-field. For each field a visual consumes, Atlan creates column-level lineage from the source dataset fields directly to that visual's analysis field—not to the visual node. This column-level lineage is nested inside the existing dataset-to-visual process, so the visual, its parent analysis, and any dashboard built on the analysis all remain lineage nodes.
- Dataset fields used in a visual take the matching
QuickSightDatasetFieldas their lineage input. - Calculated fields used in a visual carry their expression and take as inputs every dataset field the expression reaches, including through other calculated fields. For example, if
marginisrevenue - costandcostis itself a calculated field overunit_cost * quantity, the visual'smarginfield takesrevenue,unit_cost, andquantityas inputs. - Calculated fields without a dataset (no
DataSetIdentifierin Amazon QuickSight) resolve against the dataset of the visual that uses them. - A calculated field with the same name as a dataset field doesn't replace it. A reference to that name resolves to the dataset field.
Because dataset fields already carry lineage back to their source columns, you can trace a visual's field all the way to the underlying table column—for example in Amazon Athena, Amazon Redshift, or Snowflake. A calculated field whose expression references several dataset fields produces one lineage relationship per distinct field it reads.
There is no direct dataset-to-analysis or dataset-field-to-analysis lineage edge. At the asset level, each dataset links to the analysis visuals that read from it, and each visual links to its analysis. Field-level lineage always resolves to the specific field a visual consumes.
What is not covered
Field-level lineage doesn't represent the following:
- Fields used only in filters. A field that appears in an analysis filter but in no visual produces no asset.
- Calculated fields no visual uses. A calculated field defined on an analysis but not placed in any visual produces no asset. Its dataset-field inputs still appear on every visual field that uses it, directly or through another calculated field.
- Fields in dashboards. Field-to-field lineage is scoped to analyses this round. Dashboards keep their existing behavior.
- Calculated columns defined on a dataset. Amazon QuickSight doesn't return the formula for these, so Atlan can't resolve what they're derived from.
- References Atlan can't resolve, for example to a parameter, or to a field on a dataset you excluded from the crawl. Atlan skips these rather than showing incomplete lineage.
A field with no resolvable dataset-field input produces no asset and no lineage, so you won't see an orphaned field with nothing upstream.
Recrawling
Atlan rebuilds analysis field assets and their lineage on every crawl. A field's identity comes from its analysis, sheet, visual, dataset, and name, so recrawling an unchanged analysis produces the same assets rather than duplicates. Renaming a field in Amazon QuickSight, or moving it to a different visual, creates a new asset, and Atlan removes the old one on the next crawl along with any enrichment you added to it, such as descriptions or terms.