7. Mapping of Imported WSDL request/respons/fault

Introduction

When WSDL is imported, message-types are generated for each complex-type within the WSDL, and we have to implement Mapping for this with Salesforce-Objects. This support the following use cases:

• Multiple interfaces( targets) can be assigned to a single source-structure

One source-message-Type -> n targets E.g., source-data from flat file which joins Parent-child: e.g. from one source-structure -> Account + Contact

• Multiple interfaces( source-structure) can be assigned to a single target
• Simple case each source is linked to only one target and vice versa ( This is the case which we support at the moment )

Case 1:

Prerequisite

• Create Integration
• Create a MessageType that contain IStructures of Account and Contact

• Create an Inbound interface for Account and create Inbound Interface for Contact after that add Message Type with both interfaces

How to do mapping with Message Type?

• Navigate to Account Interface page detail and scroll down to Mapping section

The below screenshot shows Message Type use with account interface for Mapping

Here is Message Type use with contact interface for mapping

• Navigate to Related tab and scroll down to Foreign Key section then Create a foreign key on contact interface to lookup field account and contact sObject

• Create ichained interface in the account interface to make the parent-child interface.

• Navigate to manual load Import data

Here is a result of the message in message monitoring after pushed by the manual load.

Case 2:

Prerequisite

• Create Integration
• Create 2 MessageType for Account and Contact and join parent-child

• Create an inbound interface Account and inbound interface Contact and then add Message Type for both interfaces to do mapping

How to do mapping with Message Type?

-           Navigate to Account Interface page detail and scroll down to mapping section The below screenshot shows Message Type use with account interface for Mapping

Here is message type to do mapping for Contact interface

• Create a foreign key on contact interface to lookup field account and contact sObject

• Create ichained interface in the account interface to make parent-child interface.

• Navigate to manual load to import data

• Here is a result of the message in message monitoring after pushed by the manual load.

Case 3:

The implementation of the hierarchy’s message type and multiple related SFDC-objects. In this case, the Ichain/Interfaces are generated automatically behind the scene when source and target-structures are linked (mapped).

Prerequisite

• Create Integration
• Create a hierarchies message type E.g message type for Account and Contact as parent-child

• Create an Account interface for the parent and add message type for the interface. A note child interface is generated based on the message type with target sObject on mapping

• Create foreign key just double click on node row then choose the External ID field that mapped for parent interface.

• And here is child interface has generated automatically base on hierarchy message type that mapped with sObject

• Here is a foreign key which is created in child interface

• Then navigate to manual load to import data

Here is result data in message monitoring after pushed.