Implicit Data Mapping for Integration Objects
Data synchronization services support implicit data mapping when the internal integration object is a subset or exactly the same as the interface integration object; the reverse also holds true. Implicit mapping occurs when:
A source component maps to a target component with the same name.
A source component maps to a target component and both components have fields with the same name.
Data synchronization service does not specific a data map.
Every component, field, and child component is mapped between integration objects.
The following image shows an example of implicit mapping between two integration objects (Internal Integration Object and Interface Integration Object). In this image, components and fields with the same name are automatically mapped; data synchronization services map these fields when a data map is not specified.
In this image, the child component, Organization, which appears on the interface integration object only, is not mapped because it is not considered important to the ASI. Consequently, the two integration objects are sufficiently similar, and a data map is not necessary. Implicit mapping ignores any components and fields unique only to the interface or internal integration object, but not both.
Internal Integration Object -------- Interface Integration Object
Account -------- Account
Name -------- Name
Location -------- Location
Organization
Organization
Name
Business Address -------- Business Address
Street Address -------- Street Address
City -------- City
State -------- State
Contact -------- Contact
First Name -------- First Name
Middle Name -------- Middle Name
Last Name -------- Last Name
