Skip to main content

Overview

The Entegrata data mapping editor is a powerful visual interface for creating and managing data transformations. Using an intuitive node-based design, you can connect data sources, transform data, and map fields without writing code. This guide covers all features of the mapping editor, from basic navigation to advanced transformations.

Interface Overview

The mapping editor consists of several key areas:

Main Canvas

The central workspace where you visually build your data pipeline:
  • Source Nodes: Represent your data sources
  • Field Nodes: Individual fields from sources
  • Transformation Nodes: Data transformations and operations
  • Entity Node: Your target data type with its fields
  • Connection Lines: Show data flow between nodes
Full mapping editor interface with labeled sections

Toolbar

Located at the bottom left corner of the editor:
  • Save: Save your mapping changes
  • Discard Changes: Delete all changes made in your local session since your last save
  • View Toggle: Switch full screen and normal views
  • Fit to Screen: Auto-fit all nodes in view
Toolbar with all buttons labeled

Context Panel

Collapsible panels on the right: Context Panel - Details
  • Source Catalog
  • Entity Details
  • Source Configurations
  • Field Properties
  • Field Transformation/Combination Logic
Side panels showing source and property configurations

Map Selection

Dropdown located in the top left of the editor:
  • Select your current data map
  • Manage new and existing data maps
Data map selection dropdown

Pan and Zoom

  • Pan: Click and drag on empty canvas space
  • Zoom In/Out: Use mouse wheel or zoom controls
  • Fit to Screen: Click the fit icon to center all nodes
  • Reset Zoom: Double-click empty canvas space

Selecting Nodes

  • Single Select: Click on a node
  • Context Menu: Right click on nodes or connection lines

Working with Source Nodes

Adding a Primary Source

1

Open Source Context Panel

Click anywhere in the editor that isn’t a node or connection to open the source catalog context panel.
2

Select Source

Search and choose a source from your connected sources:
  • Database connections
  • File uploads
  • API connections
  • External systems
Source catalog context panel
3

Configure source identifier

The first source added becomes your primary source automatically. This is the main source of data for your entity.
The primary source determines the base records. All other sources are joined to this.
Configure the identifier used as primary means of identifying unique records for this source across all potentially related sources.
  • If a primary key is setup for the source, it will be the default
  • You can override the identifier to any field on the source you choose
Source catalog context panel
Related sources are joined to your primary source to enrich data.
1

Open Source Context Panel

Click anywhere in the editor that isn’t a node or connection to open the source catalog context panel.
2

Select Source

Search and choose a source from your connected sources:
  • Database connections
  • File uploads
  • API connections
  • External systems
Source catalog context panel
3

Configure Identifiers

Any source added after the first becomes a related source.
Related sources need logic defined to join to the primary source by one or more of its source’s fields.
Configure the primary key for the source if it isn’t already setup from its source. This is required to uniquely identify records from the source system.Configure how data from this source is related to the primary source using data from both sources’ fields.
  • Select a field on this source whose data uniquely relates to data in the primary source.
  • Select the field on the primary source whose data matches the selected identifier for this source.
Source identifier configuration
Join Best Practices
  • Use exact match joins when possible (e.g., ID fields)
  • Our system preserves all primary source records, but not necessarily all related source records.
  • For complex or ambiguous cases, multiple fields can be used in combination to uniquely identify records.

Configuring Source Properties

Click on any source node to view and edit properties:
  • Primary Key: Change the expected primary key
  • Identifier(s): Change the fields used to identify data between sources
  • Filters: Add filters to restrict the data used for a source

Working with Field Mappings

Direct Field Mapping

The simplest mapping: connect a source field directly to an entity field.

Drag to Connect

Click and drag from a source field to an entity field on the right side. A connection line appears. Alternatively, click on an entity field and select the source field from the dropdown.
Direct field connection

Unmapping Fields

To remove a field mapping:
  • Visual View: Right-click the connection line and select Delete or select the line and press Delete key
Context menu showing delete option

Creating Combined Mappings

Map Multiple Source Fields

1

Drag Source Field to Mapped Entity Field

Drag a a source field’s handle to a field on the entity which is already mapped.This will create a new “logic” node in the middle of the mapping editor, allowing you to specify how the different fields should be used to set the value of the target entity field.
Newly mapped "logic" node with details
2

Choose Combination Type

Select from available functions:
  • COALESCE: Use first non-null value from multiple fields
  • CONCAT: Combine multiple fields into one
  • CASE: Conditional logic (if-then-else)
  • HASH: Combine & obfuscate multiple fields to provide a uniquely random value
  • HIGHEST VALUE: Take the highest value of the input fields
  • LOWEST VALUE: Take the lowest value of the input fields
See Multi-Field Mapping for detailed guides on each.
Field combination options
3

Configure Transformation

You may now configure the logic specific to the combination type you’ve chosen. You may also now connect other source fields to the new logic node to add them to this combined mapping.

Saving and Auto-Save

Manual Save

Click the Save button in the toolbar to save your changes:
  • Saves all mapping configuration
  • Creates a version history entry
  • Does not publish to production
Save button and save status indicator

Auto-Save

The editor automatically saves your work on your browser (not the server):
  • Every change is persisted in a local state until saved.
  • Changes made only to your local browser can be discarded using the Discard Changes button in the toolbar.
  • Changes may disappear from your local browser if you clear your browser cache.

Other Controls

Full-Screen

The toolbar provides a Full-Screen view button that allows you to expand the editor view to the entire view of your screen. This provides you with more space to map your data, especially useful for larger entities.
Button to expand the editor to full screen

Re-fit View

The toolbar provides a Center view button that allows you to reset the zoom and pan of your editor back to a central position across your nodes and adjust the zoom to fit the screen.
Button to center the editor view

Troubleshooting

Editor Not Loading

Issue: Canvas is blank or stuck loading. Solutions:
  • Refresh the browser page
  • Clear browser cache
  • Check network connectivity
  • Verify you have permission to view this entity

Cannot Connect Fields

Issue: Dragging a field doesn’t create a connection. Solutions:
  • Check data type compatibility (see warning messages)
  • Ensure target field isn’t already mapped (unmap first)
  • Verify source node is properly configured

Changes Not Saving

Issue: Save button doesn’t work or changes are lost. Solutions:
  • Check for validation errors (fix before saving)
  • Verify you have edit permissions
  • Look for browser console errors
  • Try saving in smaller batches