# UploadXMLTopicFragments: Exact Online Update XML Topic Fragments Update XML Topic Fragments ## Documentation: 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.chr(13) || chr(10) || chr(13) || chr(10)chr(13) || chr(10) || chr(13) || chr(10)Additional where-clause columns supported:chr(13) || chr(10) || chr(13) || chr(10)- division - Catalog: `ExactOnlineXML` - Schema: `XML` - Alias: `xuf` - Label: Update XML Topic Fragments This is a read-only view. The Exact Online API may not support changing the data or the Invantive UniversalSQL driver for Exact Online does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Exact Online API. - Filters on API Server: division ## View Columns The columns of the view `UploadXMLTopicFragments` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `COUNT_FATAL_ERROR` | `int64` | #Fatal Error | ☑ | Number of uploads with a fatal error. | | `COUNT_NO_ACCESS_ERROR` | `int64` | No-access Errors | ☑ | Number of no-access erroneous uploads. | | `COUNT_NORMAL_ERROR` | `int64` | #Error | ☑ | Number of erroneous uploads. | | `COUNT_SUCCESS` | `int64` | #Success | ☑ | Number of successful uploads. | | `COUNT_WARNING` | `int64` | #Warning | ☑ | 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 | ☑ | Division. | | `FRAGMENT_NUMBER` | `int64` | Fragment Number | ☑ | 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_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.. | | `PAYLOAD` | `varchar2` | Payload | ☐ | Payload. | | `RESULT_ERRORS` | `varchar2` | Result Errors | ☐ | Errors and warnings in result. | | `RESULT` | `varchar2` | Result | ☐ | Result. | | `ROWNUM` | `int64` | Row Number | ☑ | Number of the row within the results, starting at 1. | | `SUCCESSFUL` | `char` | Successful | ☑ | Successful. | | `TOPIC` | `varchar2` | Topic | ☐ | Topic. | | `TRANSACTION_ID` | `int64` | Transaction ID | ☑ | Incrementing ID of the transaction. |