Overview
Datasource Management is where you connect Lens to the data that powers your analytics. Every dashboard, report, and data model in Lens traces back to a datasource registered here, which makes this the most governed surface in the product — a small number of well-named, well-maintained datasources is worth considerably more than a sprawling list of ad-hoc imports.
When to use it
Use Datasource Management when you need to register a new source of data for Lens, update an existing datasource with fresh content, reconfigure a database connection, or audit and remove datasources that are no longer in use. It’s also the governance surface for deciding who can create, edit, or delete data connections in a workspace.
Supported source types
Lens supports five categories of source, each with its own configuration path.
| Type | Description |
| Excel/CSV | Spreadsheet files — .xlsx, .xls, .csv |
| Database | Relational, NoSQL, and cloud database connections |
| Flat Files | Delimited flat file formats |
| Tally | Tally accounting software |
| Smart Sheet | Smartsheet workbooks |
File-based sources are point-in-time imports by default — they hold a snapshot of the file at import time and are refreshed when you explicitly update or override them. Database sources use Direct Connect.
Supported databases
Lens connects natively to MySQL, SQL Server, Oracle, MongoDB, PostgreSQL, Databricks, Redshift, JIRA, and Salesforce. Most connectors accept a standard set of host, port, schema, and credentials, with two notable exceptions: Oracle requires you to specify either SID or Service Name, and PostgreSQL requires an explicit database name in addition to the schema.
The datasource list
Every datasource in a workspace is listed in the Datasource Management tab, with these columns:
| Column | Description |
| ID | System-generated identifier |
| Datasource Name | Name assigned at creation |
| Type | Source type (Excel/CSV, Database, etc.) |
| Fetch Type | Method used for ingestion |
| Status | Current state — Completed or Import in progress |
| Created Date | When the datasource was first created |
| Settings | Per-row actions (see below) |
Row-level actions
Each datasource exposes five actions from the Settings column, covering the full lifecycle:
| Action | Purpose |
| Data Model | Open the data model for this datasource |
| Edit | Update a file-based datasource via Append or Override |
| Schedule | Configure a recurring refresh job |
| Delete | Permanently remove the datasource |
| Configure | Re-open the original import configuration for revision |
Update modes
File-based datasources can be updated in one of two modes. Append adds the rows from the new file to the existing data, preserving what’s already there. Override replaces all existing data with the contents of the new file — it is destructive and cannot be rolled back from within the product.
As a rule, append for incremental data, override for authoritative snapshots. When in doubt, retain the original file before running an override.
Scheduling
Scheduled refresh lets a datasource update itself on a defined cadence without manual intervention. A schedule carries a title, date and time, connector, description, and an Append or Override mode that controls how each run reconciles with existing data. Schedules depend on valid source access at run time — expired credentials, moved files, or revoked database permissions cause the schedule to fail silently until you intervene manually.
Search
For large workspaces, the search field above the datasource list performs a name-based lookup and narrows the list as you type.