24Files Winter '26 Release

Please continue reading to learn more about:

• Graph API support and upgrade instructions.

• More powerful ‘Copy Public Link’ support.

• Use the document library as record folder.

Full Graph API support

As of 24Files v6.00, 24Files works solely with the Microsoft Graph API instead of the Microsoft REST API. The choice is mostly technical and the switch has been made to make 24Files more future-proof.

Upgrade Instructions

Before you upgrade your 24Files app, you will need to upgrade the Azure Registration app, to support permission specific to the Graph API.

More details are found in the documentation here.

As part of the installation, 24Files will automatically add a Remote Site setting to access the SharePoint Graph API.

When you are upgrading from an older version of 24Files, an upgrade script will run that executes the following steps:

1. The script will logout all users and you need to login again.

2. Graph API works differently with metadata than the REST API, therefore the upgrade script will try to update automatically all object configurations that you have created. In case any of these upgrades fail, you will need to delete the old configuration manually and recreate it.

Changes to Apex Calls

If you make use of 24Flow Apex Actions, the Graph release will necessitate the following changes:

• PATH: The PATH argument does no longer require the Document Library:

  • PATH before the upgrade e.g. /Document Library/Accounts/ACME [0015I00000n0T3VQAU]/Opportunities/projectA

  • PATH after the upgrade e.g. /Accounts/ACME [0015I00000n0T3VQAU]/Opportunities/projectA

• Move Apex Action:

Support for & and %

With the Graph API, 24Files now also supports ‘&' and '%’ as part of file and folder names.

Support for SharePoint Subsites

With the Graph API, 24Files now also supports SharePoint Subsites when the full path to the subsite is in the URL, i.e. when the URL does not look like that of a regular SharePoint site.

Copy Pubic Link

The Copy Public Link file menu feature has been extended and enhanced . For this feature to work properly, you need to make sure that the settings in SharePoint are set appropriately as described below. The Copy Public Link feature in itself now allows to:

1. Define the Link Type as View Only or Edit

2. Who can access the link? Anyone or only people within the organization.

3. Expiration data of the link. If left empty, the default expiration time is taken from the 24Files Settings.

4. Password protection.

Navigate to the SharePoint Admin Center. Select your SharePoint Site. You end up on the following screen:

Navigate to the tab Settings. Adapt the File Sharing Settings:

Use the Document Library as a Record Folder

In some cases you would like to open up the 24Files component at the Document Library level rather than at the level of a designated Record Folder.

In order to support this use case, 24Files now allows you to select the Document Library as the record folder. You can configure this in the Folder Structures tab of the 24Files Manager app.

SharePoint Site and Document Library Selected by End-User

With the 24Files' Dynamic SharePoint sites feature, you can dynamically set the SharePoint site and document library per record. The Winter Release now provides the capability to give users the freedom to select the SharePoint Site and Document Library for a specific record.

If you enable Dynamic SharePoint sites and the SharePoint Reference field is empty for a record, end-users will be prompted to select the applicable SharePoint site and Document Library.

Notes & Attachments

Since a long time, you can automate the transfer from files uploaded to Notes & Attachments to 24Files and SharePoint.

In case you do not make use of this feature, but still want to occasionally upload documents to 24Files, it is possible to manual drag & drop the documents from the Notes & Attachments to the 24Files canvas.

Deprecation of Aura Component

For a number of releases, we have been supporting the Aura and LWC component in parallel. Going forward, we stop support on the Aura component and advise everyone to migrate to LWC as soon as possible. On the Aura component, users will see the following message:

General Advise

As with any major update, we recommend to install the latest version first in a sandbox and validate the functionality before moving into production.

Sub Releases

• 5.240

• 5.320

• 6.10