Data connection

Data connection is a core concept in the MatrixOne Intelligence product model. This page explains the problems it solves, its relationships with other objects, and its usage boundaries.

Definition

  • Data connection consists of connectors, load tasks, and export tasks.

  • A connector stores the source type, network parameters, and credential references, while tasks handle one-time or continuous data movement.

  • Structured sources are written to targets according to schemas and field mappings, while unstructured sources enter Catalog through files and parsing configuration.

Object relationships

  1. A connector is reusable configuration referenced by multiple load or export tasks.

  2. Loaded tables and files enter Catalog and become sources for workflows or knowledge bases.

  3. A connection can be available even when a task fails because field mappings, target permissions, and Worker status still affect execution.

Design principles

  • Use least privilege and keep credentials in managed configuration.

  • Start by validating with minimal data or test objects, then expand the scope.

  • Version executable configuration and retain each run as an execution record.

  • Do not equate a visible entry with backend availability or resource authorization.

Note

These pages follow the current MOI 5.0 product model. If an entry is missing, check the workspace, permissions, and feature flags.

Operational guidance