Application management : Tools : Enterprise Talk : Working with Enterprise Talk : Importing : Importing different UDBO types in a single run
Importing different UDBO types in a single run
It is possible to add multiple types of user defined business objects (UDBOs) in a single run. Since the import process needs to know the type of UDBO for doing an import, this information needs to be included in the XML (if necessary after a transformation) and in the import definition.
Example
BO Person has two user defined business objects:
‘UsrEmployee’
‘UsrContactpersoonExtern’
In the XML (if necessary after a transformation) the tag of the element needs to be different to identify the person type:
<?xml version='1.0' encoding='UTF-8'?>
<document>
<businessobjects>
<UsrEmployee>
<Code>000101</Code>
<LastName>Albert</LastName>
<Initials>A.A.</Initials>
<FacilityNetUsername>AAAlbert</FacilityNetUsername>
</UsrEmployee>
<UsrContactpersoonExtern>
<Code>000102</Code>
<LastName>Brown</LastName>
<Initials>B.B.</Initials>
<FacilityNetUsername>BBBrown</FacilityNetUsername>
<AddressRef>001</AddressRef>
</UsrContactpersoonExtern>
</businessobjects>
</document>
The Enterprise Talk definition needs to have two business object definitions:
1. Create an Enterprise Talk definition.
2. Add an import document.
3. Add two business object definitions:
a. One for UsrEmployee (XML node UsrEmployee)
b. One for UsrContactpersoonExtern (XML node UsrContactpersoonExtern)
4. For both UDBO definitions, add the fields as listed in the sample XML above (assumption: an address with code 001 exists in Planon).
5. For both UDBO definitions, make the Code field ‘Part of the search key’.
This is only an example, this can be any other (combination of) field(s).
6. Run the Enterprise Talk definition.
Two persons, with different UDBO type, will be added to Planon.
It is possible to update (not insert) persons with different user-defined business object (UDBO) types in a single run using only one business object definition.
* 
Since the persons are already in Planon, the XML and the Enterprise Talk definition do not need the UDBO type information.