Enterprise Talk - Import
This topic lists an excerpt of an import file including attributes.
• All data in between the <Attributes> tag is interpreted as Attributes data.
• The <Version> tag contains the version of the Attributes structure. This number is required to make sure the data within the <Attributes> tag is compliant with the implementation.
• The <AttributeDefinitionSetCode> tag contains the link to the attribute set.
• The <Values> tag contains the individual attributes.
• The type property inside the <Values> tag contains the system type of the attribute.
Your Enterprise Talk import definition must include the Attributes field, as shown in the following example:
Example
<Attributes>
<Version type="string">1.0.0</Version>
<AttributeDefinitionSetCode type="string">01</AttributeDefinitionSetCode>
<Values>
<serviceDate type="date">2018-03-31</serviceDate>
<precision type="decimal">1.33</precision>
<purchaseDateTime type="datetime">2018-03-31T14:59:00+02:00</purchaseDateTime>
<score type="integer">1</score>
<alarmTime type="time">13:30:00</alarmTime>
</Values>
</Attributes>
<Version type="string">1.0.0</Version>
<AttributeDefinitionSetCode type="string">01</AttributeDefinitionSetCode>
<Values>
<serviceDate type="date">2018-03-31</serviceDate>
<precision type="decimal">1.33</precision>
<purchaseDateTime type="datetime">2018-03-31T14:59:00+02:00</purchaseDateTime>
<score type="integer">1</score>
<alarmTime type="time">13:30:00</alarmTime>
</Values>
</Attributes>
 | The type property is currently not used during import, but might be used in the future for data validation. Currently, you do not need to specify it in the import file. |
In the following two cases, an error is displayed:
• If an attribute definition name cannot be found.
• If the combination of attribute definition name / attribute set code cannot be found.