Skip to main content

Import Data

Importing data into Boltic Tables is the fastest way to kickstart your data journey. Tables supports the following file types for import:

  • CSV (.csv) – Ideal for spreadsheets and tabular data.
  • JSON (.json) – Perfect for structured or nested data.

You can upload files up to 1 GB in size, making it easy to work with large datasets without any hassle.

πŸ“Œ How to Import Data?​

  1. Click the "Import" button on the top-right corner of your Tables workspace and "Import Data".

    File import
  2. Upload your CSV or JSON file.

    Preview file
  3. Preview the file structure β€” map file columns to table columns, update column data types, add constraints, and preview your changes.

    Edit column in preview
  4. Start Import β€” watch as the file gets converted into a fully functional Boltic Table.✨✨

  5. Track import progress in the notification and import history in the Import History page.

    Import notification

πŸ”” Important Points​

To ensure a smooth and error-free import, please keep the following formatting guidelines in mind when preparing your data.

  1. Dropdown Columns:

    • For dropdown columns with multiple options, wrap the list in double quotes and the list values in single quotes within the CSV cell.

      Example:

      days
      "['Monday', 'Tuesday', 'Wednesday']"
  2. JSON Columns:

    • The outer string should be wrapped in double quotes, and keys and values inside should use single quotes within the CSV cell.

      Example (Array of Objects):

      student_json
      "[{'id': 1, 'name': 'Alice'}, {'id': 2, 'name': 'Bob'}]"

      Example (Single Object):

      student_json
      "{'roll no': 7, 'name': 'Alstair Cook', 'hobbies': ['reading', 'traveling']}"
  3. Vectors (Dense, Half, or Sparse) Columns:

    • Always enclose vector arrays in double quotes to ensure correct parsing.

      Example:

      embeddings
      "[0.25, 0.5, 0.75, 1.0]"
      {
      "embeddings": "[0.25, 0.5, 0.75, 1.0]"
      }
  4. Date-Time Columns:

    • Use the ISO 8601 format for all date-time values to maintain consistency and timezone accuracy.

      Example:

      login_time
      2025-07-21T14:30:00Z
      {
      "login_time": "2025-07-21T14:30:00Z"
      }

πŸ“ Sample Files for Import​

To help you get started quickly and avoid formatting errors, we've provided sample files that you can download and use.

πŸ“Š Import History & Monitoring​

This section gives you a clear overview of all your import jobs β€” whether they’re in progress, completed, or failed. You can:

  • Track imports by file name, record count, and success/failure breakdown.

  • View job status in real time: Pending, In Progress, Partially Completed, Completed, or Failed.

  • Download the original file or error logs (.jsonl) if needed.

  • Search and filter by file name or status to quickly locate any import.

πŸ’‘ If your import partially fails or fails completely, download the .jsonl log file to inspect row-level errors.

File Import History
FieldDescription
File NameOriginal name of the uploaded file
StatusOne of: Pending, In Progress, Partially Completed, Completed, Failed
Total RowsNumber of rows detected in the file
Imported RowsNumber of rows successfully imported
Failed RowsNumber of rows skipped due to validation or parsing errors
ActionsπŸ”½ Download file, πŸ“„ Download logs (if any)

🧠 Tips & Best Practices​

  • Importing large files? Ensure clean formatting to minimize failed rows.

  • Tables automatically manages the id, created_at, and updated_at columns. However, if your uploaded CSV or JSON file contains values for these fields, the system will map those values directly to the corresponding system columns. This allows you to import historical or external data with full fidelity.