Transaction XOG export does not contain the required ExternalID

Document ID : KB000122387
Last Modified Date : 04/12/2018
Show Technical Document Details
Question:
After exporting a transaction, the XOG file is missing the required externalID. Is this a defect or by design? 

This prevents the import into a new system. This is the error message upon import: 

</ErrorInformation> 
<ErrorInformation> 
<Severity>FATAL</Severity> 
<Description>[Error] :1:1: element "Transaction" is missing "externalID" attribute 
</Description> 
<Exception type="java.lang.Exception">Invalid xml data</Exception> 
</ErrorInformation>
Answer:
The External ID is for XOG in transactions from external systems, not taking from one clarity instance to another. 
To XOG in transactions, they typically come from another , external source and the external ID is added into the XOG file.
We purposely do not give that field when we read out the XOG transactions from clarity because the read out is meant only to be exported 1 time 
for integration purposed, not for migrating data to another instance.

To export the financials from timesheets from one Clarity to another, what you have to do is import the timesheet and run it through the jobs.
The suggestion to import the timesheet data instead of transactions and let the system generate transactions through the normal process.