#How to upload a stuck Draft Record – TrueContext Help & Support

Looking for information about TrueContext features and functionality? Visit our Product Documentation Portal.

Description: Every day we get tickets that have a title something like this:

You can mostly find them in the view labeled "Draft (Tier1 Unassigned)". We need to upload them for the client to get their data. There can be different reasons why the client sends the Draft forms to us. For example, if there is an error while they open the draft form they tend to send the draft forms for us to upload them manually. It is wise to ask the customer about the reason why they sent those draft forms.
Because it is worth investigating the cause of the issue to provide a long-term solution.

Steps:

Open the ticket and go to the bottom of the page. At the bottom, you might see a zip file like this:
OR You Might see a folder path like the following instead:
Problem Draft DR for user 1319059024

Location path: 1/124509001/device-storage/1319059024/25023921009/problem_drafts/2024-07-03_09-39-52_1173481E-BDEB-4049-9CCF-938C79DA309F.zip

Note: "1" is the last number of the Team ID, "124509001" is the team ID, "1319059024" is the user ID, "25023921009" is the device ID
Just in case you didn't receive the email from the client with the Draft S3 path, you can check the pathname by building the S3 pathname according to the IDs as explained in the Note above.
If you don't have the zip file in the ticket, you would need access to the S3 browser. Copy the path from the first number (from the 1 at the beginning of the above example) to "problem_drafts/" and put that into the Search bar in the S3 Browser.
There you will see the zip file and you can download the file/files to your local computer.
Note: If you see a large number of draft forms in the S3 browser folder, please check which form needs to be uploaded by looking at the last folder name in the location path that the customer sent you.
As a good practice, keep a copy of the original Zip file in case there is an issue where the original file is lost, you'll want your copy.
Extract the Zip file.
The formatting of the filename for the zip will look something like this:
20240702160113-1530849004+1319059024+v5_35.zip
Where the "20240702160113" is the date and time down to the millisecond of submission, "1530849004" is the Form Iteration ID, "1319059024" is the user ID, "v5_35" is the protocol version.
Note: The name of the Zip file can vary depending on the Operation system of the device.
If your Zip file doesn't have the following format in the name, you have to change the Zip file name to have the following format.
<date and time down to the millisecond of submission>-<Form iteration ID>+<User ID>+<Protocol verstion>
Eg: 20240702160113-1530849004+1319059024+v5_35
Note: You can find the form iteration ID by searching the "iterationId" in the data-record.json file.
If the extracted zip folder has the form definition file, please delete that.
Change the .json file name to "data-record.json".
Note: In some cases, the .json file might be in cdr.json format like below. Please rename it to "data-record.json".
Open the "data-record.json" file in a Notepad and change the value in the "status" field from "Saved" to "Complete"
Change the .manifest file name to "manifest.json"
Note: If the manifest file doesn't exist in the folder, please create a text file and rename it with "manifest.json" (change the extension to .json while renaming)
Then you can add the following format into the manifest.json and fill the following data.
```
{
"size": 278620,
"file_name": "data-record.json",
"client_dr_id": "add the client DR ID",
"attachments": []
}
```
-size: The size of the data-record.json file in bytes (you can open the properties window of the data record file and see the size in bytes)

-file_name: leave the file name as "data-record.json"
-client_dr_id: You can find the Client DR ID by searching the keyword "clientDataRecordId" in the data-record.json file

-attachments: Feel free to leave the empty square brackets [] since it is not mandatory.
If there are any attachment files only leave the attachment name like below. (attach_xx_yy)
Check the data-record and manifest file to see if all the attachment files referred to in those files exist in this extracted folder
Note: You can search the attachment references in data-record file using the keyword, "contentType"

If there aren't any attachments missing, please skip step 14 below.
If you notice any attachment referred to in the data-record or manifest file is missing in the extracted zip folder, you must ask the customer if they provide their consent to us to upload the draft record without the missing attachments.
--> If they provide you with their consent, please remove the missing attachment references in data-record and manifest files and Save the changes.
-->If they don't provide their consent for us to upload, we won't be able to upload the draft form since there are missing attachments.

If the manifest file is missing in the folder, however, if the data-record.json has all the attachment references and all the attachments are included in the folder, the manifest.json file can still have the attachments section as empty square brackets [] and everything will still be uploaded properly.

If the manifest file is missing in the folder, and the attachment references mentioned in the data-record.json are not included in the folder, please ask the customer if the submission can be uploaded without the missing attachments.
After following all the steps above, save the folder as a zip file to compress it.
Logging to the Live web portal using your administrator account.
Click System Administration > Manually Upload Submission
On the page that loads you will click the "Upload file" button and find the zip file. Upload that.
If the upload was successful, the following page will reload and you can view the uploaded submission using the "View Uploaded Submission" option under the "Actions" menu.
If there was a failure, please check in Sumo Logs and see what could be the reason for the error.
Once the record is uploaded update the ticket to tell them it is uploaded successfully and what the reference number is. You can then solve the ticket.