What is the role of a Connector data source in OneStream?

What is the role of a Connector data source in OneStream?

• A. It interfaces with the source system via API to bring data into OneStream
• B. It stores data locally in OneStream
• C. It defines a mapping for data sorting
• D. It is used to export forecast data to external systems

Answer: (A)

In OneStream, a Connector data source acts as the bridge to external systems. It uses APIs or prebuilt connectors to reach the source system, pull data, and bring it into OneStream. This role focuses on how OneStream accesses the data—defining endpoints, authentication, and data formats—so the data can be ingested and processed within OneStream. It doesn’t store data locally as its primary function; storage happens in OneStream after ingestion. It also isn’t responsible for sorting or mapping data—that happens through separate data-mapping and load rules once the data is brought in. And exporting forecast data to external systems is handled by other processes, not the Connector data source.

In OneStream, a Connector data source acts as the bridge to external systems. It uses APIs or prebuilt connectors to reach the source system, pull data, and bring it into OneStream. This role focuses on how OneStream accesses the data—defining endpoints, authentication, and data formats—so the data can be ingested and processed within OneStream.

It doesn’t store data locally as its primary function; storage happens in OneStream after ingestion. It also isn’t responsible for sorting or mapping data—that happens through separate data-mapping and load rules once the data is brought in. And exporting forecast data to external systems is handled by other processes, not the Connector data source.