Changelog

Select multiple nodes on the Relationship Canvas and act on them as a unit. Multi-select stays responsive on canvases with hundreds of nodes.

What's new

• Hold Shift to extend the selection to a range.

• Drag a marquee to capture every node in an area.

• Group, recolor, or export the cluster as a sub-graph.

How to enable

1. Open any project on the Relationship Canvas.

2. Toggle Multi-select in the canvas toolbar.

3. Use Shift, marquee, or Cmd-click to build your selection.

Fixed a memory crash when importing CSVs over 50MB.

What changed

• Parser is now stream-based with a 4MB read buffer.

• Failed rows isolate with line number and reason instead of aborting.

• Encoding detection covers UTF-8, UTF-16, and Windows-1251.

Profile search is now 4x faster on collections with more than 5000 entries. Existing collections reindex automatically on first open.

Highlights

• Phone numbers, aliases, and domains return matches in under 100ms.

• Prefix queries — typing +44 7 surfaces every UK mobile.

• Field-scoped queries like email:acme.com narrow results to one column.

Apply tags or field updates to many profiles at once, directly from search results.

How it works

1. Run any query in the search bar.

2. Select all matches or pick specific profiles with checkboxes.

3. Edit a field or attach tags in a single action.

Use cases

• Tag every profile linked to a specific case file.

• Reassign analyst-owners after a team change.

• Mark stale profiles in bulk during quarterly audits.

Every change is reversible from the audit log and respects collection permissions.

The profile schema is split into Person, Organization, and Asset entity types. Existing profiles auto-migrate to Person on first open.

What's new in each entity

• Person: jurisdiction, citizenship, and known aliases as structured fields.

• Organization: ownership share, parent-org reference, industry codes.

• Asset: wallets, properties, and accounts with chain-of-custody fields.

Action required

1. Update export-API paths from profile.field to profile.person.field.

2. Review the migration guide before rolling out self-hosted updates.

3. Test integrations that depend on the old flat schema.