Complex Data Mapping Techniques

Chained and Any-to-Many Data Mapping

  • Mapping to/from any number of inputs
  • One to one, one to many, many to one, etc.
  • Specifying file names with wildcards
  • Specifying file names in database tables
  • Support for auto-number sequences
  • Chain an unlimited number of components
  • Chain output to be input of another target
  • Each chained component is a modular entity
  • Ability to preview output at each step in the chain
  • Automate transformations with MapForce Server

Any-to-Many Data Transformation

MapForce makes it easy to define complex data integration, conversion, and ETL processes. The input and destination of a data mapping can be mixed formats, including any combination of XML, JSON, PDF, databases, flat files, EDI, Excel, XBRL, etc. A data mapping project can have one input mapped to one output, one input to many outputs, many sources to one destination, or many sources to many destinations, all in different data formats, as shown in the example to the left where Excel data is mapped to JSON and XML files.

MapForce lets you integrate data from multiple files and data sources or split data from one source into many outputs. Multiple files can be specified through support for wildcard characters (e.g., ? or *) in filenames, a database table, auto-number sequences, or other methods. This feature is very useful in a wide variety of data integration scenarios; for example, it may be necessary to integrate data from a file collection or to generate individual XML files for each main table record in a large database.

MapForce also allows you to use file names as parameters in your data integration projects. This lets you create dynamic mappings in which specific file names are defined at run-time.

One to many data mapping project

Learn how One-to-Many Data Mapping Works

Chained Data Mapping

Chained data mapping in MapForce

Support in MapForce for chained or multi-step data transformations empowers you to create complex mappings in which the output of one mapping becomes the input of another. This powerful feature adds to MapForce's ability to execute fully automated transformations for complex data integration and ETL scenarios. Each chained component becomes a modular entity in an interdependent transformation sequence, allowing for conversions to be made on-the-fly.

Chained transformations can be created using any number of mapping components connected to a final target component. Previews can displayed/generated for intermediate components, as well as for the final mapping result.

Intermediate mapping components have a "pass-through" button in the title bar. This button lets you define the set of data passed on to the following component.

Create a Chained Data Mapping in MapForce

Output Preview

When a data conversion produces dynamic output of multiple files, each file has its own numbered pane in the Output preview window. A convenient menu option lets you save all the output files in a single step.

For chained transformations and mappings producing multiple distinct output components, an icon on the component lets you assign it to the output preview window.