Before you start an upload, review the information available in the Introduction to TDI article and follow the guidance provided in the article.
To see a list of the specific field mapping table articles, skip to the Entity field mapping table articles section in this article.
Upload sequence and order of operations
There are three main TDI entity dependency categories that determine the upload order sequence.
- Entities that are dependent on other entities.
- Note: These will be noted as Prerequisites in the entity mapping tables found in the TDI section of the Help Center.
- Entities that are not dependent on other entities.
- Entities that are not dependent on other entities but may be more easily configured if certain entities are uploaded first.
Due to these considerations, we recommend uploading entities in the following order (as needed):
- Other account
- Routing Guide
*Note: If you have a single contact that is associated with multiple entities (Parent, Factor, Carrier, Customer, Other account, and/or Location), you can upload the Contact entity before the Parent and other account-related entities. If you do so, when you are configuring these other entities, you can plug in the contact.csv’s context ID into the other entities’ files in multiple areas, such as the Primary contact or Billing contact. However, if you do not have a contact that is associated with multiple entities, it may be easier to upload the Contact entity after the account-related entities, so that the contact can be configured with the correct IDs for the account they are associated with.
**Note: If the Contact entity was uploaded between the User and Parent entities, do not upload it again between Location and Asset. Otherwise, upload the Contact entity between Location and Asset.
Considerations for upload order
While you are not required to upload your files in this exact sequence, we highly recommend following the order outlined above to allow entities to be mapped with each other at the time of upload. A newly uploaded entity cannot reference information from another entity that does not exist yet.
For example, the Factor entity can technically be uploaded before the User or Contact entity. However, the following columns in two of the Factor entity’s files are dependent on IDs found in the other entities:
- The primaryContact.id column in factor.csv references the unique system ID for a contact, found in the id column of the Contact entity’s contact.csv file.
- The user column in user_commissions.csv references the unique system ID for a user, found in the id column of the User entity’s user.csv file.
If the Factor entity is uploaded before these other entities, then the columns must be left blank when uploading the Factor entity’s files. If you wish to provide contact and commission information for factors, you will need to fill in the user and contact information manually in your factors’ profiles on your Turvo tenant at a later time.
Step-by-step upload guide
Login and click on your profile icon in the top right corner. Select Admin console from the drop-down.
Click on the Turvo data importer tile.
Click DOWNLOAD TEMPLATE to access the list of available templates.
Select the entity you wish to update from the drop-down.
Once selected, you will see all available template files for that entity. The file listed first is the mandatory file, and all others are optional files.
Download the templates by clicking the DOWNLOAD button. All mandatory and optional files will be downloaded as a .zip folder.
Mandatory vs optional files are not obviously marked, but there is a simple way to tell which is which:
- Mandatory files always have the name of the entity as the file name (Ex: user.csv)
- Optional files are all other files that are not named as the entity.
Open the folder to access the templates and fill them in using the field mapping tables within this document.
What to expect in the downloaded .zip folder:
- Mandatory file
- This is a required file to upload that specific entity.
- This file will always have the name of the entity as its name (entityname.csv)
- Optional file(s)
- Not required for successful entity data upload.
- They are provided to add more information for each entity.
Refer to the articles linked in the Entity field mapping table articles section for the corresponding entity to understand how to fill in the .csv columns.
Once the template has been filled out, save the document as a .csv file.
Click the upload button to upload the files.
An Upload files modal displays. Select the entity you would like to upload from the list. Once selected, the list of available mandatory and optional upload files for that entity will appear.
Upload files must be dragged and dropped or selected into the correct slot for the template type. Always place the mandatory file in the top file slot in the Upload files modal.
Optional files must be placed in the correct slot in order to correctly upload. For instance, if you are trying to upload a contact_info optional file, you must place it into the contact_info slot.
See screenshot below which shows the user uploading the mandatory file along with the contact_info file. Note how the files are named as well. Click PROCESS to start the upload.
You will be taken back to the Turvo Data Importer dashboard where you can check the status of the import. New imports will show up in Processing status and may take a few minutes to a few hours to process depending on the file size and time of day.
See the next section on TDI Dashboard for important areas to focus on in the dashboard.
The TDI Dashboard is where you can view a summary of information about any current or past uploads. The dashboard indicates upload status, errors, and has information required by Turvo Support should you need to reach out to us for assistance.
Review the table below to understand dashboard columns. Each row in the table corresponds to a column shown in the TDI Dashboard.
Unique ID for the upload which you must provide to Turvo Support when reaching out for TDI troubleshooting assistance. This is what allows Turvo to investigate a particular upload.
Displays the entity being uploaded. Note that only one row is created per upload. For example, you will not see a separate row for each .csv file uploaded simultaneously for a single entity.
Indicates the status of the upload. See Upload statuses below for additional information on each status type.
This shows the number of successful rows vs the number of total rows attempted. For successful uploads, the numbers should match.
Indicates the user who performed the upload.
Indicates the date/time of the upload.
Indicates the last time that an update was received from the platform. Once an upload is completed, this field should not change.
Statuses displayed in the Status column indicate whether the upload was successful. Use the status displayed to understand what steps to take if your upload did not complete successfully. The Action column indicates recommended troubleshooting steps. These troubleshooting steps should be followed prior to reaching out to Turvo Support.
Indicates the system is working on completing the upload. An upload may be in this status for a few minutes to a few hours depending on the file size and time of day. Turvo throttles upload speed during peak working hours to reduce load on the system.
Uploads that are too large to process are terminated by the system. Any upload that processes for more than 5 hours will be terminated.
The file contained errors which prevented successful upload.
Check the corresponding errors .csv file that appears in the Errors column of the Dashboard.
All rows were successfully uploaded.
Completed with errors
Some rows were successful while some rows were not.
If your import comes back with a status of Failed or Completed with errors, an error file will be created and available for download in the right pane pop-out when the upload job line is selected:
Click the DOWNLOAD ERROR FILE button available in the right pane column to download a copy of the error.csv to your computer to view the details of the error and next steps to resolve the error.
Entity field mapping table articles
You can find the appropriate field mapping tables and their prerequisites for upload in the following articles. Click the link to open the article in a new tab.
- TDI field mapping tables - Group
- TDI field mapping tables - User
- TDI field mapping tables - Parent
- TDI field mapping tables - Factor
- TDI field mapping tables - Carrier
- TDI field mapping tables - Customer
- TDI field mapping tables - Other account
- TDI field mapping tables - Location
- TDI field mapping tables - Contact
- TDI field mapping tables - Asset
- TDI field mapping tables - Items
- TDI field mapping tables - Order
- TDI field mapping tables - Shipment
- TDI field mapping tables - Routing Guide