Using Functoids to Create More Complex Mappings
Microsoft BizTalk Server 2004
Using Functoids to Create More Complex Mappings

Functoids play a crucial role in many mapping scenarios. Without functoids, you can copy element and attribute data, but you cannot, to any significant extent, manipulate the values themselves. Using functoids, almost any transformation is possible. For example, with a functoid you can take two values from entirely different locations, add them together, and place the sum in the destination schema.

Functoids appear in the Visual Studio .NET Toolbox, one toolbox tab per category, when you are editing a BizTalk map. After you open the Toolbox and choose a category of functoids by clicking on the corresponding tab, you drag the functoid onto a grid page. Then you create input and output links between the functoid and either schema nodes or another functoid. Input links correspond to input parameters and lead to a functoid from the left; an output link corresponds to the output parameter and leaves a functoid to the right.

Like other map elements, functoids have properties. One of the most important properties of a functoid is its set of input parameters. For more information, see Adding Basic Functoids to a Map.

This section provides step-by-step instructions for working with functoids within BizTalk maps. For reference information about functoids, organized by category, see Functoid Reference.

This section contains:

To download updated BizTalk Server 2004 Help from www.microsoft.com, go to http://go.microsoft.com/fwlink/?linkid=20616.

Copyright © 2004 Microsoft Corporation.
All rights reserved.
© 2009 Microsoft Corporation. All rights reserved.   Terms of Use | Trademarks | Privacy Statement
Page view tracker
Rate the Lightweight library
x
Lightweight builds on ScriptFree (loband) by adding features you've requested: a SearchBox and default code language selection.
Do you like the SearchBox?
Do you like the tabbed code blocks?
How useful is this topic?
Tell us more.
Thanks
x
You're helping to improve MSDN Online.
Feedback
Switch View
Classic
Lightweight Beta
ScriptFree
Switch View