Application management : Tools : Enterprise Talk : Examples - import : Importing workspaces
Importing workspaces
This topic describes how to import workspaces by using Enterprise Talk.
* 
When adding or updating a workspace, you also need to include the workspace detail. If the workspace detail is not included, an error will be shown.
Typically, the space code itself is not unique, which is why space, floor and property are also added. In this case, the space, floor and property already exist so they are only used as search fields and the BOs themselves are skipped. The import document should therefore have five business elements that are interlinked.
Field configuration
Business Object level
Import policy
Field (system name)
Field as …
Part of search key?
Property
Skip
Code
Yes
Floor
Skip
Code
Yes
Property
Sub
Yes
Space
Skip
Code
Yes
Name
Floor
Sub
Yes
WorkSpace­Details
Create/update
BeginDate
No
Space
Sub
Yes
WorkSpace
Super
Yes
WorkSpace
Create/update
Name
No
Code
Yes
BeginDate
Yes
AvailableArea
No
Import XML sample
<?xml version='1.0' encoding='utf-8'?>
<document>
<businessobjects>
<WorkSpace>
<Code>100</Code>
<Name>Workspace</Name>
<BeginDate>2023-4-15</BeginDate>
<AvailableArea>1</AvailableArea>
<WorkSpaceDetails>
<Space>
<Code>1.42</Code>
<Floor>
<Code>01</Code>
<Property>
<Code>14</Code>
</Property>
</Floor>
<Name>WS1.42.a</Name>
</Space>
<BeginDate>2023-4-15</BeginDate>
</WorkSpaceDetails>
</WorkSpace>
</businessobjects>
</document>
After import: a fixed workspace starting on 15-4-2023 is added to Planon for property 14, floor 1, space 1.42.