Browse and Preview Source Data

Browse and preview are the first data checks after a connector can reach its source. Use them before mapping source values to operational targets.

When to use this page

Use this workflow when:

• a connector test succeeds;
• you need to find the correct tags, fields, topics, objects, tables, or files;
• the source owner needs to confirm units and meaning;
• mappings are being prepared for Inspector, AI Agent, predictive maintenance, or BI.

Browse workflow

1. Open Data Integration > Connectors.
2. Open the connector.
3. Start the connector if browsing requires an active connection.
4. Open source browse.
5. Navigate through source hierarchy.
6. Select candidate nodes or fields.
7. Record source paths that should be mapped.

What "source hierarchy" means depends on connector type:

Source type	Browse may show
OPC UA	Namespace, objects, variables, nodes.
BACnet	Devices, objects, properties.
Modbus	Register groups or configured register map.
MQTT	Topics or configured payload fields.
REST	Response fields from the configured endpoint.
CSV	File columns.
JDBC	Tables, columns, or query result fields.

Preview workflow

1. Select a source node or field.
2. Run preview.
3. Check recent sample values.
4. Confirm timestamp.
5. Confirm data type.
6. Confirm unit.
7. Confirm expected range.
8. Mark the field ready, uncertain, or rejected.

What to record

For every candidate field, record:

Item	Why it matters
Source path	Needed for mapping.
Display name	Helps reviewers recognize the field.
Source owner	Needed when values look wrong.
Timestamp field	Required for time-based workflows.
Unit	Needed for conversion and quality checks.
Expected range	Helps detect impossible values.
Target asset or point	Needed for operational context.
Review state	Ready, uncertain, or rejected.

Preview review checklist

Approve a source field for mapping only when:

• the value is current enough for the workflow;
• timestamp is clear;
• equipment or asset identity is clear;
• unit is known;
• value range is plausible;
• source owner can explain the field;
• the same field is not duplicated under a better source path.

Common problems

Symptom	Likely cause	Action
Browse fails	Connector is not running, source is unreachable, or permission is missing.	Start connector and recheck credentials/network.
Preview is empty	Source path has no recent data or query is too narrow.	Ask source owner and adjust path or query.
Timestamp is missing	Source payload has no usable time field.	Add timestamp mapping or choose another field.
Values are stale	Upstream source stopped updating or interval is too long.	Check source system and sync strategy.
Values look impossible	Unit, scale factor, byte order, or field selection may be wrong.	Review connector configuration and mapping transform.

Next step

After preview confirms the right source field, continue with Mapping Source Fields.