Various issues can arise when your importing data in the TrackVia system. Typically, issues are due to malformed spreadsheets data consistency issues. However, there are many other types of issues that you can run into.
This article should help you troubleshoot those issues. It's broken down into "Generic Issues" which could occur anytime in the importing processes, and "Import Errors" which show up in the error report after the import completes.
If you are still having trouble importing your data into TrackVia after using this article, please contact TrackVia Support.
Issue: Import taking a long time to complete
Possible cause 1: The most likely reason is that the import is causing many app scripts to run and those are taking a long time to complete. There are two options to account for this. 1) Disable the app scripts on import. 2) Simplify the app scripts so they take less time to execute.
Possible case 2: Adding or updating records in the table is causing many triggered fields to run. The more triggered fields there are, the longer each record will take to save. You can either convert the triggered fields to calculated fields, or you can reduce the number of triggered fields. Check out the Building Performant Applications course to learn more about app performance.
Issue: Data got imported into the wrong fields
Possible cause 1: The method you chose for import was to copy and paste data in a tab or comma separated format. If the data itself contains tabs or commas as text other than for the reason on delimiting fields, then you may end up with incorrect data mappings. To fix this, first paste the data into a spreadsheet, save it as an .xlsx field, then import the spreadsheet instead.
Possible cause 2: There are merged cells in your spreadsheet and TrackVia. TrackVia is unable to interpret merged cells. Unmerge the cells and re-import.
Issue: DENIED!!! error when creating a table
Possible cause: This error will occur when you are importing to create a table, you’ve specified that at least one field will be a dropdown or checkbox field, and there were no values listed in the data for that field. This can be resolved by adding the dropdown or checkbox options to the data in the spreadsheet before importing. You can always go remove them after the import has finished.
Issue: Import completes but no records got added or updated
Possible cause 1: This is most likely due to an app script that ran into a runtime exception. The error report that’s sent via email will likely contain the app script errors. Please refer to the App Script Troubleshooting article for information on resolving the error, or disable the app scripts when importing.
Possible cause 2: The table has a group field set as the record ID. You can resolve this issue by changing the record ID to a different field, rerun the import, then change the record ID back to the original settings.
Issue: Import wizard never progresses past the file upload screen
Possible cause: This is likely due to formatting issues within the spreadsheet. Please refer to the How to Prepare your Spreadsheet for Import article then rerun the import after making the necessary changes.
Error: Whoops! We seem to have encountered an error. Don’t worry though, your data is still safe. Please contact TrackVia Support if the problem persists.
Possible Cause: This error appears as an orange error message in the bottom right corner of the screen, immediately after starting the import. This message will appear when an app script timeout occurs. Please refer to the App Script Troubleshooting guide, or reach out to the TrackVia support team to inquire about increasing the app script timeout limit for that table.
Error: The record ID "XYZ" does not uniquely match a value in the parent table "ABC".
Possible cause 1: There is no matching parent. Make sure that the parent record does in fact exist, that the imported value matches the text of the parent ID exactly, there are no trailing or leading spaces, and that there are not multiple spaces between words.
Possible cause 2: There are duplicate parent records. This can be resolved by removing the duplicate record, or by changing the record ID of the parent table to something more unique.
Error: There are multiple records for the record ID consisting of values "ABC"
Possible cause: This error means that there were more than one record in the table with the same record ID. TrackVia could not determine which of the multiple records should be updated. To fix the issue, either dedupe the table so there is only one matching record, or change the record ID to be more unique.
Error: There are no records for the record ID consisting of values "ABC"
Possible cause: This error occurs when there was no record found in the table with the specified record ID. This can be resolved by either adding the new record manually, or by rerunning the import as an Import to Update and Add rather than just an Import to update. See the How to Import to an Existing Table article for more information.
Error: The field “ABC” is empty and is part of the Record ID.
Possible cause: This error is produced when one of the fields that make up the record ID does not have a value in it in the import file. To resolve the issue, make sure the data is present in the import file.
Error: Invalid DROP_DOWN/CHECK_BOX value "XYZ" for column name "ABC"
Possible cause: The value that you are attempting to import into a drop down or checkbox field does not exist. If the value you are importing does not exist in the field settings in TrackVia, add it. If it does exist, make sure the spelling is exactly the same in the spreadsheet and in the field settings in TrackVia. If there is a difference, you can make the adjustment in the spreadsheet or in the TrackVia table.
Error: Invalid DATETIME value "5.1.23" for column name "ABC"
Possible cause: The format of the column in the spreadsheet does not match the necessary formatting for the field type in TrackVia. You can resolve this by changing the format of the data in the spreadsheet. Dates should be formatted as “mm/dd/yyyy” and date times should be formatted as “mm/dd/yyyy hh:mm A/PM”.
Error: "Execution of the user script for table ""ABC"", event type ""BEFORE_INSERT"" failed…
Possible cause: This is an error caused by an app script runtime exception. To resolve the issue, please refer to the App Script Troubleshooting guide, or disable the app scripts when running the import.