Question On Usage of Common Mapping Functionality In BizTalk RRS feed

  • Question

  • Hi All,

    I have a scenario where we have different maps for various end requests Transformation.  

    All these maps has a node whose mapping is common in all the maps. Hence I am planning to put the mapping out of individual maps and storing it in some place and then calling it inside the individual maps.

    This common node mapping is complex and contains approx 200 elements. There are some custom logics as well.

    Please add your comments for this problem task.




    Saturday, May 13, 2017 5:51 AM

All replies

  • Best practice is to use a canonical, decoupled pattern for your message flow

    For common parts of the schema eg address (invoice, customer, shipping etc) import an address schema with own namespace
    You can use the same mapping/xslt for the address in outgoing formats eg edifact (orders, desadv, invoic etc) 
    It can be added in scripting functoid or used as part of handcoded custom xslt to use in a map

    hth  /Peter

    Saturday, May 13, 2017 8:17 AM
  • What you're describing is an interim Canonical message, essentially a superset of all data the trading partners need.

    Yes, this works very well.  You have the one Map with all the common logic, then individual maps that adjust the content for a specific trading partner.

    What you'll probably have for a trading partner map is one with mostly direct links except where changes are necessary. This is common in EDI scenarios where each trading partner has only minor differences in an otherwise common transaction.

    Saturday, May 13, 2017 4:24 PM
  • ... essentially a superset of all data the trading partners need.

    Yes pr message type

    It will be easy to eg add a new subsidiary with independent accounting/sales systems as only one set of new interfaces needs to be implemented if at all

    Plan for the future

    rgds /Peter

    Sunday, May 14, 2017 10:02 AM