How-to
Article Markdown

How to export and import knowledge base chunks

Bulk-update chunk text and enabled status in a Fast Line Pro knowledge base via Excel or CSV — with conflict checks before apply.

When you need this

  • You need to fix wording across dozens or hundreds of chunks quickly.
  • You want to enable or disable many chunks in one file.
  • You need to compare the live knowledge base with a spreadsheet and apply only verified edits.

What to know

  • Only chunk text and enabled status change. Documents, order, and IDs are not created or deleted via the file.
  • Removing a row from the file does not delete the chunk. Adding a new row does not create a chunk.
  • If someone changed a chunk in the UI after export, import shows a conflict and will not overwrite it blindly.
  • The feature may be disabled on the instance. If you do not see the buttons, ask an administrator (toggle FastLine dataset tabular export/import in instance settings).
  • Import accepts only .xlsx or .csv files with a matching file type; other formats are rejected.
  • After apply, agent search may still show previous chunks for a short time (reindexing).

Before you start

Steps

1. Export chunks

  1. On the documents page, open Export (Вивантажити in Ukrainian UI).
  2. Choose:
    • Entire knowledge base — Excel (.xlsx) — recommended for manual editing;
    • Entire knowledge base — CSV;
    • Selected documents — Excel or CSV (enabled only when documents are selected).
  3. Wait until the file is ready and download it.
  4. Check the success message for document and chunk counts.

2. Edit the file

  1. Open the Chunks sheet (Excel) or the CSV table.
  2. Edit only the chunk text and enabled columns (true / false).
  3. Do not change identity or signature columns — those rows will be rejected.
  4. Save as .xlsx or .csv (up to 25 MB).

3. Import and preview

  1. Click Import changes.
  2. Optionally use Download current template for a fresh file.
  3. Choose the file and start validation.
  4. Review Changed, Unchanged, Conflicts, and Errors.
  5. Download the report for problem rows if needed.

4. Apply changes

  1. The apply button shows the exact change count. It stays disabled when there are zero changes or a blocking file error.
  2. If conflicts or row errors exist, confirm that valid rows may be applied while conflicts/errors are skipped.
  3. Confirm apply and wait for the result.
  4. Download the result report if needed.

What happens next

Only validated chunks are updated. Conflict rows stay as they were at apply time. The documents list refreshes after a successful or partial apply.

How to verify

  • The import result shows applied / unchanged / conflict / error counts.
  • Open a document and check a chunk you edited.
  • Re-export and re-import the same file without edits should show zero changes.

Other options

  • To move an entire knowledge base between instances, use Marketplace packages — not tabular import.
  • For a single chunk, edit it on the document segments page.
Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request