| Version | Description | |
|---|---|---|
| 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 ‘Record per Site’ 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 ‘Record per Site’ and ‘Folder in Site’. · Trigger Handler: Multiple small bug fixes · Fix a small bug that creeated 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 Saleforce 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.28 | Fixes · Changed sharing setting on Refresh process to allow overwriting/deleting File 365 records even when the current user has no access. | |
| 3.27 | Fixes · Changed sharing setting on Download process to allow overwriting Salesforce Files even when the user has no access. | |
| 3.26 | Fixes · Error on Refresh from SharePoint when no folder is present. | |
| 3.25 | Fixes · Error querying Document Libraries when the Named Credential URL contains Upper Case characters. |