BizTalk Maps and the Table Looping/Table Extractor Functoids

When dealing with existing systems, sometimes a challenge presents itself in the form of a flat file.   Trying to impose structure upon a flat file can be achieved, however, using the Table Looping and Table Extractor functoids.  Consider the following schemas:

Source schema:
 

FlatLoanSchema

Target schema:
 

LoanSchema

One’s first attempt at a map to transform the source to destination might look something like this:
 

MapAttempt1

We’ll use the following input file to test the map.
 

InputFile

The output isn’t quite what we were hoping for.
 

Attempt1

The Table Looping functoid is the key to what we’re trying to achieve.  Below is the map that uses the Table Looping and Table Extractor functoids to create the desired output.
 

MapAttempt2

The Borrower fields are used as inputs into the Table Looping functoid as well as some definitions about how many rows and columns there will be.
 

TableLoopingInputs

By opening up the Table Looping Grid, we’re able to define what fields will go into certain columns/rows:
 

TableLoopingConfiguration

The Table Extractor functoids are used to define which columns from the table map to use as inputs.  Each Table Extractor functoid corresponds to a column within the Table Looping Grid.
 

TableExtractor

And finally the output from Table Looping functoid to the Borrower node dictates that a Borrower node be created for each row within the Table Looping Grid.  With that said, here’s the output from testing the second map:
 

Attempt2

 Source code for this example can be found here.

This article is part of the GWB Archives. Original Author: Evan Koch

New on Geeks with Blogs