Release notes

Release Notes

7 min readUpdated 17 November 2026
VersionDescription
5.0.3
November 17, 2026
Fixes
  • The “Large file uploads” step on the Connection Setup page now shows the right size limit: files larger than 23 MB need it. Before, it said 11 MB.
  • When you click Retry on a file that failed to upload and the upload continues in the background, the file now shows as Queued until the upload is done. Before, the Retry button stayed available, and a second click started a second upload of the same file.
  • A file on a record without an Object Location, or whose Object Location only creates SharePoint sites, now gets the status Error, and Retry shows why. Before, the file stayed Queued for good.
5.0.2
November 13, 2026
Fix
  • When downloading a synced file fails with an error from Microsoft, such as a Conditional Access policy that blocks downloads, the File 365 log now shows Microsoft’s message instead of “Unknown Error”. The full response from Microsoft is saved in the log’s Debug field.
5.0.1
November 5, 2026
Fixes
  • The Connection Setup page now has its own white background. Before, in orgs whose Lightning theme has a background image, the image showed through behind the setup steps.
  • The Apex unit tests no longer fail in orgs without the “Minimum Access – Salesforce” profile, such as orgs created before Winter ’23. The tests that need this profile are skipped there.
5.0
November 3, 2026
New Features
  • Connection Setup page. A new page in the File 365 Administration app lists each setup step and shows which ones are done.
  • Guided SharePoint connection. Administrators enter the Microsoft 365 details on the Connection Setup page. File 365 checks them with Microsoft and then creates the Named Credentials itself, so they no longer have to be created by hand.
  • Large file uploads up to 2 GB. Files larger than 23 MB are now uploaded to SharePoint in parts, in the background. An administrator turns this on once, under “Large file uploads” on the Connection Setup page.
  • File previews. A setup step on the Connection Setup page lets SharePoint previews show inside Salesforce.
Enhancements
  • New Object Locations use the standard File 365 Named Credentials by default. You can still choose different ones.
  • New Flow action that creates the SharePoint location of records in the background.
  • Clearer error messages when SharePoint can’t create or rename a site.
  • When a deleted record’s SharePoint folder has no files left, the folder now goes to the SharePoint recycle bin.
  • Improved Apex unit tests, with many new tests of real-life scenarios. The tests fill in your org’s own required fields and pass your duplicate rules, and skip the parts your org’s setup doesn’t allow, such as a blocking validation rule or no Email-to-Case. So they no longer fail your deployments.
Fixes
  • When you retry a large file from the Gallery, the retry now runs in the background instead of failing.
  • Deploying a trigger from the Manage Trigger page no longer ends with the error “Apex type not found for element locationsCovered” in orgs on the Winter ’27 release. The trigger was deployed, but the page didn’t confirm it.
  • When a File 365 record is deleted and its synced Salesforce file is also on another record, the file is now removed from the File 365 record’s own record and stays only on the other record. Before, it stayed on both, or was removed from the other record when the user couldn’t see that record.
  • When a file is deleted in SharePoint, a refresh now also deletes its Salesforce copy when another user downloaded that copy. Before, the copy was left behind without a File 365 record.
4.17.18
October 22, 2026
Enhancements
  • Deleted SharePoint files and folders are moved to the SharePoint recycle bin instead of being deleted permanently
  • Deleting a parent record whose lookup is set to “Delete this record also” now also deletes the SharePoint files and synced Salesforce files of its File 365 records
  • Salesforce files that are also linked to another record are no longer deleted
Fixes
  • Fix error when deleting a File 365 record of an object without an Object Location
  • Fix detection of folder trees deeper than 5 levels when cleaning up old folders after a merge
4.17.17
October 13, 2026
Enhancement
  • Align with new Winter ’27 Apex limits to allow for larger file uploads and downloads
Fix
  • Remove binary content from debug log messages
4.17.15
October 7, 2026
Fix
  • Fix refresh issue for Object Location using All (wildcard) objects.
4.17.14
October 7, 2026
Fix
  • Fix issues for users without a File 365 license on objects where File 365 is configured
4.17.13
October 7, 2026
Enhancement
  • Better handling of downloads for a SharePoint backed file directly from the browser.
4.17.12
August 4, 2026
Fixes
  • Fix issue in refresh from SharePoint with files exceeding 2GB in size
4.17.11
July 30, 2026
Enhancements
  • Update of Gallery components to match new Lightning Design System v2 styling
  • Add larger drag-and-drop section in Gallery component for easier upload of files
4.17.10
May 19, 2026
Fixes
  • Fix an issue where downloading a file from SharePoint could fail without a resulting error message.
4.17.9
April 28, 2026
Fixes
  • Fix an issue where template folder creation fails when using a subfolder path in the Object Location
4.17.8
April 10, 2026
Fixes
  • In a batch process sometimes a single error could cause the remaining items to fail silently
4.17.6
April 7, 2026
Fixes
  • Add security check on classic Refresh webservice method
  • Change test methods to run on non-english environments.
4.17.5
April 4, 2026
Fixes
  • Fixes issue where unlicensed users cannot add notes to records of object having a File 365 Object Location
4.17.4
March 25, 2026
Fixes
  • When there are folders at a tree depth of 5, an exception occurs
4.17.3
March 18, 2026
Enhancements
  • Allow operation on objects up to API version 64.0
4.17.2
March 16, 2026
Fixes
  • Issue resolved where changing the subfolder did not move files on SharePoint when using the Site per Record Object Type.
4.17
November 11, 2025
Enhancements
  • More detailed and descriptive error messages
4.15
May 27, 2025
Enhancements
  • Allow created site to be registered as Hub Site (when using Site per Record type)
  • Enhanced code security
4.13.1
April 2, 2025
Fixes
  • Fix log issue when refreshing from non-existing SharePoint site.
  • Fix issue when building the URL when refreshing from SharePoint
4.13
February 5, 2025




Enhancements
  • Show created date on File 365 records.
  • Show file size on File 365 records.
Fixes
  • Prevent Synchronizing files from SharePoint when the size exceeds the maximum (11MB)
  • Prevent unneeded background processes when using Email-to-Case when no Object mapping is in place for the Case object.
4.12
January 22, 2025


Fixes
  • Improved Thumbnail download error handling
  • Better filtering of characters that are illegal to use on SharePoint folders and URLs.
  • Issue resolved with refreshing files from SharePoint where subfolders are used.
  • Issue resolved when using custom folder permissions with document templates.
4.11.2
January 2, 2025
Fix
  • Issue resolved where a relative folder URL prevented setting the permissions in Sharepoint.
4.11
December 11, 2024








Enhancements
  • Possibility to use a different Named Credential for folder creation and set permissions of created folders in SharePoint. This can be used to prevent users from changing the SharePoint folder structure while providing users with the needed contribute permissions on the created folders.
  • SharePoint Site Title will be changed on SharePoint if the corresponding field on Salesforce changes.
  • Ability to upload Files to SharePoint directly into a subfolder (needs Before Trigger)
Fixes
  • Ensure SharePoint location did not always work for location type Site per Record
  • Document Template filter issue when using location type Folder per related record in site
  • Issue when handling Email Messages without ParentId
4.10.1
July 12,2024
Enhancement
  • When refreshing files from SharePoint less Memory and CPU is needed. This allows for significantly more files in SharePoint to sync to Salesforce.
4.9.2  
June 6, 2024  
Enhancement
  • When a Before Flow Trigger and/or Apex Trigger edits the created File 365 record, those changes are taken into account
4.9.1  
April 6, 2024
Fixes
  • Solves issues when having a special character in the subfolder field.
4.9  
April 5, 2024
Fixes
  • Prevent errors for users without access to File 365 Object Location records.
4.8.2
February 5, 2024  
Fixes
  • Document Templates did not work with Object Location Type ‘Site per Record’ and ‘Folder in Site’.
  • Trigger Handler: Multiple small bug fixes
  • Fix a small bug that created multiple unnecessary error logs on refresh.
4.8.1  
November 28, 2023
Fixes
  • Hide ‘Manage Trigger’ button for wildcard Object Mappings
  • Better error handling when Object Location is not found when File 365 Toolbox or Gallery is visible on a record page.
4.8  
November 22, 2023



 
Improvements
  • File 365 Gallery
    • Header button layout changed to a single row.
    • Header upload button drop zone removed.
    • Dropzone added to component when no files are available.
    • Improved handling based on the size of the applicable lightning page region.
4.7.7
June 18, 2024 


Enhancements
  • When a Before Flow Trigger and/or Apex Trigger edits the created File 365 record, those changes are taken into account.
Fixes
  • Solves issues when having a special character in the subfolder field.
4.7.6  
February 5, 2024  
Fixes
  • Document Templates did not work with Object Location Type ‘Site per Record’ and ‘Folder in Site’.
  • Trigger Handler: Multiple small bug fixes
  • Fix a small bug that created multiple unnecessary error logs on refresh.
4.7.5
November 28, 2023
Fixes
  • Hide ‘Manage Trigger’ button for wildcard Object Mappings
  • Better error handling when Object Location is not found when File 365 Toolbox or Gallery is visible on a record page.
4.7.4
October 3, 2023
New Feature
  • The Subfolder or Site URL fields are not required to be required fields any more. Files will be moved to SharePoint when the field is filled. Clearing the field is not allowed.
Enhancements
  • Allow all buttons and upload selection on all Lighting Components.
  • Easy deployment of necessary Apex Trigger on objects enabled for File 365
  • Subfolders are allowed Document Templates.
  • Document Templates files attached create empty template folders.
Fixes
  • Changing the subfolder field works when containing a / = having subfolder(s).
  • Prevent clearing of the File Name.
  • Add handling of inbound messages created with the Salesforce Outlook add-in.
4.6.1
July 18, 2023
Fixes
  • Add several components to the File 365 Permission Set.
4.6
June 23, 2023
New Feature
  • Changing the Subfolder Field on the Salesforce records renames the corresponding folder on SharePoint.
  • Merging records in Salesforce merges the files and folders in SharePoint.
Enhancements
  • Allow for longer file and folder names.
  • Better handling of API call throttling to SharePoint.
4.5
June 14, 2023
Fixes
  • Add f365_API method to enable the rename and merge features
4.3.2
July 18, 2023
Fixes
  • Add several components to the File 365 Permission Set
4.3
June 1, 2023  
Changes
  • Issue solved when refreshing files in Gallery component.
  • Better support for OneNote Notebooks
4.2
May 26, 2023
Fix
  • Synchronize from SharePoint added on page load in Gallery component
4.1
May 23, 2023
Fix
  • Several File 365 Gallery UI improvements
3.30.1
April 6, 2023
Fixes
  • Memory optimizations to allow for record folders with lots of files on Sharepoint.
  • Solve an issue when a Content Version is inserted without the PathOnClient field.
3.30
February 22, 2023
Changes
  • Characters in the file name that are illegal in SharePoint, will be replaced by an _ (underscore)
  • If the filename was changed because it already existed on SharePoint, or because it contains illegal characters for SharePoint, the related synced File in Salesforce is renamed as well.
Fixes
  • After the upload of a new File, a refresh deleted the File 365 record created by the upload. This only happened if the upload to SharePoint completes during the processing of the results from SharePoint.
3.29  Fixes
  • Inserts of multiple ContentVersion records using the FirstPublishLocationId field when running Asynchronous, results in an error.
3.28Fixes
  • Changed sharing setting on Refresh process to allow overwriting/deleting File 365 records even when the current user has no access.
3.27Fixes
  • Changed sharing setting on Download process to allow overwriting Salesforce Files even when the user has no access.
3.26Fixes
  • Error on Refresh from SharePoint when no folder is present.
3.25Fixes
  • Error querying Document Libraries when the Named Credential URL contains Upper Case characters.

Was this article helpful?

Need more help?

Our support team is happy to help.

Contact support