New in List & Label 31: Export Reports to S3, SharePoint and OneDrive

With List & Label 31, exporting reports to cloud storage becomes significantly more flexible. Instead of temporarily storing reports locally and then processing them further via a custom upload process, export is now possible directly to modern cloud storage targets. As soon as applications run in containers, on servers, or generally in more distributed environments, local file paths quickly become impractical.

Cloud storage providers in List & Label 31 for S3, SharePoint and OneDrive

What’s new in List & Label 31?

The most important innovation: List & Label 31 introduces native support for two new cloud storage provider paths. New providers for S3-compatible storage and Microsoft Graph are now included. This allows reports to be transferred directly to Amazon S3 or Cloudflare R2, as well as to SharePoint and OneDrive.

S3-compatible storage

Reports can be exported directly to S3-compatible storage. This includes not only Amazon S3, but also services like Cloudflare R2, Wasabi, or MinIO. Access is handled via access key and secret, without integrating an additional SDK. This is especially practical if your application already relies on object storage or if reports are automatically fed into existing processing workflows or stored as backups in the cloud.

Microsoft Graph provider

Also new is a Microsoft Graph provider for SharePoint and OneDrive. This allows reports to be stored directly in Microsoft 365 environments without building a separate export and upload workflow alongside it. This is particularly useful in business applications: many teams work with SharePoint document libraries or OneDrive storage. If reports arrive there directly, they automatically become part of the users’ existing work context.

Why is connecting cloud storage important?

In many applications, the actual export is no longer the final step. Generated documents often need to be passed directly into an existing infrastructure: into an object storage bucket, a team folder in SharePoint, or personal storage in OneDrive. This is exactly where things have often been unnecessarily complicated until now.

The traditional approach usually looked like this: generate report, temporarily store it locally, integrate an upload script or custom SDK, transfer the file, then clean up the temporary file. While this works, it involves additional manual effort and is far from elegant, especially in containerized or scaling setups.

With the new cloud storage providers in List & Label 31, this detour is eliminated, and exports land directly in the cloud storage of your choice.

A few typical scenarios

  • S3 for server-side processes: your backend generates invoices, delivery notes, or analyses and stores them directly in a bucket where other services can process them further.
  • SharePoint for team documents: reports are stored in project or department folders so that teams can work with them directly.
  • OneDrive for personal storage: individual analyses or exported documents are immediately available in the user’s personal workspace.

The real advantage of the new cloud storage providers is above all: less glue code, fewer temporary files, and less special logic.

Who benefits most from this new feature?

List & Label 31 with its new cloud storage providers is particularly interesting for teams that want to:

• integrate reports automatically into existing cloud workflows,
• already use Microsoft 365 environments productively,
• rely on S3-compatible object storage,
• reduce local export paths and downstream upload processes,
• or modernize their reporting infrastructure for more advanced deployment scenarios.

This is also where the real strength of List & Label becomes clear: reporting solutions tailored to your specific use case and perfectly aligned with your existing application.

Related Posts