For the complete documentation index, see /llms.txt. The full corpus is available at /llms-full.txt. Most pages have a raw markdown variant; append .md to the URL or send Accept: text/markdown.
PricingComplianceCareersBook a demo

Docs  |  User Guides

Import

The Import page is your gateway for bringing data into the app. It is organized into two tabs: Files for uploading data from local files, and Integrations for viewing hardware and software connections that push data into Invert automatically.

Files Tab

This is the primary method for uploading bioprocess data from files. Pick a file (or folder), choose a mapping template, and press 'Start Import' to initiate ingestion.

  • Step 1: File or Folder Picker

    Select one or more files from your computer using the file picker. Supported file extensions include .csv, .xls, and .xlsx. You can upload multiple files at once, as long as they share the same file structure. Folder upload is also supported — select a folder and all files inside will be uploaded using the same mapping. It is recommended to carefully review files before ingestion to avoid importing faulty data.

  • Step 2: Mapping Picker

    Select a mapping template that best fits your data structure. Several mappings are available to support the following data types: Run Data, Timeseries Data, or Run Events. Custom mappings can be added to the list upon request. Refer to the mapping example in the top right corner of the screen or consult the Mapping Guide below for more information on a particular mapping.

    When you upload a file, Invert will automatically suggest a mapping if it can infer the format from your file's structure. Accept the suggestion with 'Apply mapping' or dismiss it to choose manually.

  • Step 3: Settings (Timeseries Data Only)

    When importing timeseries data, you have the option to either 'merge' or 'replace' existing datasets. Choose 'merge' to update an existing dataset by either overwriting or appending data. Alternatively, select 'replace' to discard the existing dataset for a given metric and replace it entirely with the imported data.

  • Step 4: Start Import

    Click the 'Start Import' button to initiate file ingestion. This will direct you to the 'Importing' page where you can review 'Import details' for more information on ingestion status. Depending on the file size, file ingestion may take up to several minutes to complete.

  • Step 5: Ingestion Evaluation

    • Step 5.1: Successful File Uploads

      Upon file ingestion, ensure data imported into Invert meet your expectations. Click 'Runs' or 'Metrics' for a comprehensive overview on the imported data. Consider editing and re-uploading files to update or replace data inside the app as needed.

    • Step 5.2: Failed ingestion attempts

      Failed file ingestions may occur if the source file contains unexpected or incomplete data, or if the file structure is not supported by the selected mapping. Consult the error log on the Importing page for details and verify the file meets the mapping criteria. Contact Invert support via Help & Support if you need further assistance.

Ingestion Preview

Ingestion Preview lets you see exactly what will be imported before any data is committed. For single-file uploads, Preview is on by default — Invert processes the file and shows a structured summary of what would be created, organized into tabs (Runs, Library, Timeseries, Events, Lineage) so you can catch mapping issues or unexpected data before they land in your workspace. Each tab name shows a count of items, and tabs with zero items are grayed out and non-clickable. The Library tab lists the unique metrics and properties detected in the file so you can verify nomenclature before approval. Click Approve to proceed with the actual import, or go back to adjust the file or mapping. Folder uploads skip the preview step.

Mapping Guide

  • Run Data
    • Description: Metadata associated with a run
    • Example: LOT#, Reactor ID, Site, Operator
    • Mapping: 'Run Data'
      • Required Columns:
        • Run
        • Metric A (unit)
      • Recommended Columns:
        • Experiment
  • Timeseries Data
    • Description: Time-based metrics
    • Example: Time (h) versus Temperature (**°**C)
    • Mapping:
      • Timeseries Data (absolute time)
        • Required Columns:
          • Run
          • Timestamp
          • Metric A (unit)
      • Timeseries Data (relative time)
        • Required Columns:
          • Run
          • Time (h) or Time (min)
          • Metric A (unit)
  • Run Events
    • Description: Notes associated with a run.
    • Example: Reactor Foaming @ 24h EFT
    • Mapping:
      • Run Events (absolute time)
        • Required Columns:
          • Run
          • Timestamp
          • Event Type
      • Run Events (relative time)
        • Required Columns:
          • Run
          • Time (h) or Time (min)
          • Event Type
  • Invert Data
    • Description: Import data from an Invert export file
    • Example: Time (h) versus Temperature (**°**C)
    • Mapping:
      • Invert
        • Required Columns:
          • Export file structure generated by Invert

Integrations Tab

The Integrations tab lists all configured data sources for your organization — hardware agents, ELN connections, and other automated data streams. Clicking a data source opens its detail page where you can review connection status and recent ingestion activity.

Import History

Navigate to the Import History page for an overview of all historical file ingestions. Select a specific upload to see details on mappings used, runs created, and metrics imported. You can also download the original source file from this view.

ExperimentsRuns