The following are release notes for the Tetra SharePoint Online Connector v1.1.x. The Tetra SharePoint Online Connector is a standalone, containerized application that uploads files from SharePoint Online site folders to the Tetra Data Platform (TDP).

v1.1.0

Release date: 20 March 2026

TetraScience has released Tetra SharePoint Online Connector version 1.1.0. This release adds support for non-default document libraries and includes bug fixes for file uploads that have special characters in their filenames.

Here are the details for what's new in Tetra SharePoint Online Connector v1.1.0.

Prerequisites

• SharePoint Online Sites and corresponding document libraries
• Tetra Data Platform (TDP) version 3.6.0 or later
• A Microsoft enterprise application with credentials that the Connector can use along with authorization permissions to access files and their metadata in SharePoint Online sites

New Functionality

New Functionality includes features not previously available in the Tetra SharePoint Online Connector.

• Non-Default Document Library Support: The Connector now supports polling files from non-default document libraries by specifying the optional driveId field in the source path configuration. If driveId is not specified, the Connector polls the default document library, preserving backward compatibility. For more information about how to find the driveId, see the Connector README in the TDP.
• Automatic Polling Context Migration: When upgrading from v1.0.0, the Connector automatically migrates existing polling context (delta sync state) to the v1.1.0 internal key format, ensuring incremental sync continues from where it left off, rather than re-syncing all files.
• SharePoint Subsite Configuration: Customers can now configure the siteId for SharePoint subsites using the comma-separated siteCollectionId,webId format. Subsite support has not been extensively tested across all SharePoint configurations. If you encounter issues, contact TetraScience support. For more information, see Configure the Connector for SharePoint Subsites in the Tetra SharePoint Online Connector User Guide (v1.1.x).

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

• There are no enhancements in this release.

Bug Fixes

The following bugs are now fixed:

• The Connector now handles filenames with special and unicode characters that previously caused the following error when setting Amazon S3 metadata headers during file upload: TypeError ERR_INVALID_CHAR: Invalid character in header content

Limitations

The following are known limitations of Tetra SharePoint Online Connector v1.1.0:

• The Connector retrieves the latest file version at the time of polling. This means that multiple edits made in SharePoint between polls may be represented as a single version in the TDP.
• If files in SharePoint Online are renamed or moved, then the file version is uploaded as a distinct file at a new file path in the TDP.
• The Connector does not support polling the root directory of a document library.
• If multiple sourcePaths in the Connector configuration have overlapping paths, files found in multiple sourcePaths may be uploaded with the sourceType and labels of an arbitrary source path.
• The Connector supports polling non-default document libraries by specifying the driveId in the source path configuration. If driveId is not specified, the Connector polls the default document library.
• The Connector uploads checksums from Sharepoint's Graph API to the TDP, but does not verify the SharePoint quickXorHash hash. Customers seeking additional data integrity verification may verify the hash by using a code snippet like the one found in Code Snippets: QuickXorHash Algorithm in the Microsoft documentation.
• Syncing a large SharePoint document library may risk exceeding Microsoft Graph API limits. If the Connector reaches a daily limit, polling may be paused for up to a day because of SharePoint throttling. The Connector will broadcast throttling as a change in health status and a descriptive error. Because of this throttling risk, customers should carefully plan their Connector deployments and manage their enterprise application access credentials. For more information about SharePoint throttling, see Avoid getting throttled or blocked in SharePoint Online in the Microsoft documentation.
• The Connector will try to upload a file version from SharePoint three times before marking the upload as failed. Once a file version is marked as failed, the Connector will not attempt to re-upload it. If an upload error occurs, users can resolve the issue and perform actions like delete and restore the file, change file contents, update SharePoint document library metadata, move the file to a new directory, or rename the file to increase the file version and permit a re-upload of the file to the TDP.

Deprecated Features

There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

There are no known issues in this release.

Upgrade Considerations

Upgrading from v1.0.0 to v1.1.0
Customers can upgrade directly to Tetra SharePoint Online Connector v1.1.0 from v1.0.0 with no configuration changes needed. The Connector automatically migrates existing polling context when it first runs.

Important: The automatic migration for the default document library only occurs when driveId is not specified in your source path configuration. This is because v1.0.0 only supported the default document library (no driveId). If you want to explicitly specify a driveId for the default document library after upgrading, run the Connector once without the driveId first to trigger the migration. Adding a driveId immediately will cause a full re-sync (no duplicates in the TDP, but increased API calls and longer sync times for large folders).