Entity mapping

An entity mapping forms a dependency between a target entity and a source entity. Entity mappings can be created into loads and they can contain attribute level mappings. Agile Data Engine uses entity mappings to generate workflows and attribute level entity mappings to generate loads.

See also:

• Entity mapping types

• Loads

• Entities

• CONFIG_LOAD_TRANSFORMATIONS

Tutorials

See the below videos for quick tutorials on how to create entity and attribute mappings.

Creating entity mappings

Entity mappings are created into loads:

1. In a load view press Create entity mapping.

2. Find a source entity using the search, press Select entity and the entity mapping view is opened.

3. Use the entity mapping view to add attribute level mappings.

4. Add new attributes into the target entity by selecting attributes from the source entity (left side) one by one or with Select all and by pressing Map selected by name:

Note that this creates new attributes into the target entity unless attributes with identical names already exist in the target entity.

5. You can also edit the name of a new attribute before mapping it into the target entity or use Select from existing attributes to pick an existing target attribute instead of creating a new one. Press Map and add when finished:

6. Map attributes from the source entity into an existing attribute in the target entity (right side) with Add source attributes. Select a TRANSFORMATION TYPE and press Save:

7. When necessary, define entity mapping type and position:

Notes

• An existing entity mapping can be edited by clicking an entity mapping name in the load view. Changes to attributes will automatically be updated to entity mappings unless there are CUSTOM transformations that e.g. explicitly refer to attributes.

• Loads can have multiple entity mappings. However, Agile Data Engine can only generate a load automatically when there is one entity mapping of type SOURCE or SOURCE (Driving Run ID Logic). Use OVERRIDE load steps when multiple SOURCE type entity mappings are necessary.

• Attribute mappings are optional yet recommended if OVERRIDE load steps are used.

• Check the generated load from the entity Summary tab with Export SQL.

• When creating an outgoing load, the wizard navigates directly into a new entity mapping in the target entity. See Loads for more information.

• Add new transformations or edit existing transformations with CONFIG_LOAD_TRANSFORMATIONS.