Data Model Mapping

The Data Model Mapping document in Astera allows users to define how metadata is mapped between source and target data models during data transfer operations. This document will go over how we can use Data Model Mapping in Astera.

01-data-model-mapping

Use Case

To get started, go to File > New > Data Model Mapping in Astera. This opens the Data Model Mapping editor. Here, let's start configuring our mapping by first selecting the Use Case from the dropdown:

• Database Copy: For standard data transfer between databases.

• Dimensional Modelling: For mapping data to dimensional models (star/snowflake schemas).

• Migration: For data migration scenarios. This option enables additional features like Source System Key and Lookup mapping type.

Next, configure the data model paths:

• Source Data Model Path: Browse and select the source data model (.mdl) file that contains your source entities.

• Target Data Model Path: Browse and select the target data model (.mdl) file that contains your target entities.

Source System Key (Migration only): Enter a unique identifier to help identify records from the source system. Once both data model paths are set, the editor loads the entities from both models.

Entity Mappings

The left panel displays a tree view of all target entities from your target data model. Click on a target entity to select it. For the selected target entity, configure:

• Target Entity: Displays the selected target entity name.

• Source Entity: Select the corresponding source entity from the dropdown.

Field Mappings

Once you select a target entity, the Field Mappings Grid displays all fields from that target entity. For each field, configure:

1. Target Field: The name of the target field.

2. Mapping Type: Select how this field should be mapped:

• Direct: Maps a source field directly to the target field.

• Expression: Use this when you want to map the target field based on any expression/transformation.

• Lookup (Migration only): Look up a value from another entity based on matching fields.

1. Source Column: The source field or expression that maps to this target field.

Generate and Refresh Mappings

Generate All Mappings: Automatically generates mappings for all entities based on matching field names.

Refresh All Mappings: Refreshes mappings when source or target models have changed.

Generate Entity Mappings: Generates mappings only for the currently selected entity.

Refresh Entity Mappings: Refreshes mappings only for the currently selected entity.

Using the Mapping File

Once configured, save the mapping document. The file is saved with a .dmap extension. To use the mapping file, reference it in the Database Copy workflow task by providing the file path in the Mapping File Path property.

We have now successfully configured our Data Model Mapping document in Astera.