XML Target Connector works on the simple principle of organizing the elements into tables or fields. The unbound elements segregates and considered as separate tables.
To explain how an XML Target Connector works, let us consider the sample XML file of Customer Account/Address details.
The following image shows a sample XML file of Customer Account/Address details:
The following image shows a sample XML file of Customer Account/Address details:
Table-1: Table CustomerAccountSummary_Customers_Customer with XPath /CustomerAccountSummary/Customers/Customer
Table-2: Table Accounts_Account with XPath CustomerAccountSummary_Customers_Customer_Accounts_Account
Table-3: Table Accounts_Account_PhoneNumbers_Phone with XPath /CustomerAccountSummary/Customers/Customer/Accounts/Account/PhoneNumbers/Phone
Table-4: Accounts_Account_Addresses_Address with XPath /CustomerAccountSummary/Customers/Customer/Accounts/Account/Addresses/Address
Note: Any bound element to the former element becomes the child element of the former element. For example,
•Phone numbers is the child element of Accounts.
•Accounts are the child element of customers.
Note: All simple and attribute elements are considered as fields. Complex elements are not considered as fields to the table.
The following image shows the option to view tables in cloud target:
The following image shows the relations between different tables:
•Table-1 and Table-2 has a parent-child relation.
•Table-2 is parent to Table-3 and Table-4.
The following image shows the sibling relation between tables:
