---
title: "UploadXMLTopicFragments (Exact Online)"
description: "Update XML Topic Fragments"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/exactonline/ExactOnlineXML.XML.UploadXMLTopicFragments
original: https://documentation.invantive.eu/en/datamodels/exactonline/ExactOnlineXML.XML.UploadXMLTopicFragments
updated: 2026-11-01T17:55:09Z
license: https://documentation.invantive.eu/en/
---

# UploadXMLTopicFragments: Exact Online Update XML Topic Fragments

`read only` `XML`

- Catalog: `ExactOnlineXML`
- Schema: `XML`
- Label: Update XML Topic Fragments

Update XML Topic Fragments

Can only retrieve data.

## Summary

Individual fragments upload XML topics using the table UploadXMLTopics. After fragmentation to meet Exact Online size limitations, a fragment is uploaded to the XML API of Exact Online. The outcome of each upload is registered as a single row in UploadXMLTopicFragments. Each fragment can contain many objects, such as sales invoices. Each individual object can fail uploading into a selected Exact Online company. The collected errors can be found in the column RESULT_ERRORS. An XML text containing solely the payload to retry failed objects is available in the column PAYLOAD_RETRY_FAILED. This XML text can be copied into a text file and manually uploaded through the Import/Export XML menu option of Exact Online to reconstruct missing data.

Additional where-clause columns supported:
- division

## API Source

- XML topic: `UploadXMLTopicFragments`

## Performance Characteristics

| Characteristic | Value |
|---|---:|
| Estimated rows | 500 |
| Estimated size (bytes) | 0 |

## Table Columns

The columns of the table `UploadXMLTopicFragments` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `COUNT_FATAL_ERROR` | `int64` | #Fatal Error | [x] |  | Number of uploads with a fatal error. |
| `COUNT_NORMAL_ERROR` | `int64` | #Error | [x] |  | Number of erroneous uploads. |
| `COUNT_NO_ACCESS_ERROR` | `int64` | No-access Errors | [x] |  | Number of no-access erroneous uploads. |
| `COUNT_SUCCESS` | `int64` | #Success | [x] |  | Number of successful uploads. |
| `COUNT_WARNING` | `int64` | #Warning | [x] |  | Number of uploads with a warning. |
| `DATE_ENDED_UTC` | `datetime` | Date Ended | [ ] |  | Date and time at which the upload ended (UTC). |
| `DATE_STARTED_UTC` | `datetime` | Date Started | [ ] |  | Date and time at which the upload started (UTC). |
| `DIVISION_CODE` | `varchar2` | Division | [x] |  | Division. |
| `FRAGMENT_NUMBER` | `int64` | Fragment Number | [x] |  | Number of fragment within transaction. |
| `ORIG_SYSTEM_GROUP` | `varchar2` | Original System Group | [ ] |  | Original system group. |
| `ORIG_SYSTEM_REFERENCE` | `varchar2` | Original System Reference | [ ] |  | Original system reference. |
| `PAYLOAD` | `varchar2` | Payload | [ ] |  | Payload. |
| `PAYLOAD_LENGTH` | `int32` | Payload Length | [ ] |  | Payload length in characters. |
| `PAYLOAD_NODE_COUNT` | `int64` | Payload Node Count | [ ] |  | Payload number of topic nodes. |
| `PAYLOAD_RETRY_FAILED` | `varchar2` | Payload to Retry Failed | [ ] |  | Payload to retry to load the failed elements.. |
| `RESULT` | `varchar2` | Result | [ ] |  | Result. |
| `RESULT_ERRORS` | `varchar2` | Result Errors | [ ] |  | Errors and warnings in result. |
| `ROWNUM` | `int64` | Row Number | [x] |  | Number of the row within the results, starting at 1. |
| `SUCCESSFUL` | `char` | Successful | [x] |  | Successful. |
| `TOPIC` | `varchar2` | Topic | [ ] |  | Topic. |
| `TRANSACTION_ID` | `int64` | Transaction ID | [x] |  | Incrementing ID of the transaction. |



## Release Notes

What changed per release in the tables, columns, attributes and capabilities of the driver:

- [Exact Online](/en/release-notes/drivers?driver=exact-online)

