v3.
...
6
Install Filenize v3.1 6 for Production or Sandbox
Note |
---|
The |
...
version name for this release is incorrectly listed as 'Winter '21.' This will be corrected in the next release. This discrepancy does not affect the functionality of the package. The correct label should be 'Summer '24.' |
Fixed an issue with uploading files that contained certain special characters.
Resolved a permissions issue that occurred when deleting old logs.
Added an alert to notify users about a credentials reset when changing the authentication provider.
Introduced a new "Data" tab in the Filenize Config. This page enables Filenize admins to clear Filenize Logs, with more features planned for future updates.
Reduced overhead in the initial Filenize automated action call, resulting in a slight performance improvement.
v3.5
Fixed an issue with the ‘Type__c' field on 'Field_Column__c' that lacked the new picklist value 'Choice.'. (the value still needs to be added manually to support Choice columns, but won’t result in an error anymore. You can review the 3.4 note below on how to add the picklist value)
Fixed an issue wherein the Filenize invocable actions would stop due to a 'Tunnel through proxy' error, specifically identified as error 503. Similar to standard 503 errors, these are now automatically retried after a brief delay.
Fixed an issue where Filenize configuration would break when an unsupported Auth Provider was selected.
Fixed an issue with the polling mechanism which would not stop properly on location change.
Added a new path format that would wrap on path level instead of spaces. In addition, the last level is now bold.
v3.4
Note |
---|
Salesforce does not update picklist fields with new Managed Package updates. If you have Filenize installed below version v3.4 and if you are utilizing Choice columns in SharePoint and encountering difficulties with the "Sync with SharePoint" button on the Metadata page, consider applying the following workaround:
This issue will be resolved in the upcoming update. If you do not utilize Choice columns, this will not affect you. We apologize for any inconvenience this may have caused. |
Fixed an issue where the "Skip if no user is found" flag was being ignored when the underlying user exists, but its Active Directory (AD) counterpart changed its internal email.
Fixed an issue where the “Load More” button was not shown on certain folders.
Fixed an issue where the Last Modified Date was not shown properly.
Fixed an issue where some features were not activated without the service user.
Added an advanced search prompt to help search on indexed columns to prevent the 5000+ items SharePoint error (https://support.microsoft.com/en-us/office/manage-large-lists-and-libraries-b8588dae-9387-48c2-9248-c24122f07c59?redirectsourcepath=%252fen-us%252farticle%252fmanage-large-lists-and-libraries-in-office-365-b4038448-ec0e-49b7-b853-679d3d8fb784).
To support indexed columns, we now show a key icon to indicate that the column is indexed.
Added the functionality to load folders using other values from the record than its Id. This for example allows you to show object-wide folders and folders per lead/opportunity/case status. Options are limitless in combination with formula fields.
Show a pinning icon to indicate that the current folder is pinned. It also shows the pinning value when hovering over the icon.
Added support for Choice type column fields.
Shows all possible values in the Metadata configuration.
Shows a picklist with all options when creating new folders/files (and the column is set as editable).
...
v3.3
Minor UI bug fixes.
Minor performance/caching fixes.
Added support for coloring folders through a new invocable action
This does not currently color the folders in Filenize; it only affects Sharepoint Online. Microsoft has not yet released the updated icons in their styling framework. We will monitor this change and apply the update to Filenize once it is available.
...
v3.
...
2 (AppExchange Ready Patch)
The update permission for Filenize objects has been added to the Filenize User permission set.
Additional FLS checks applied and added more asserts to unittests (AppExchange ready!)
v3.1
Note |
---|
Due to certain packaging conflicts, the UPDATE permission for the Filenize Action, Filenize Action Run, and Filenize Action Group objects is currently not included in the Filenize User permission set. As a temporary workaround, please grant these permissions in an alternative permission set. The permissions are included in the new 3.2 release, which is coming soon. We apologize for any inconvenience this may cause. |
Added the option to disable folder and file edits in the UI.
Added a filter to the header showing the current running action and flow diagnose to only show actions that are triggered by the same SharePoint instance.
Added the Provider Instance field to the Filenize Action object.
Automated the deletion of old log records after 30 days.
Fixed an issue that shows the parent folder even though the option is disabled.
Fixed an issue showing an error about nodes when “No folder related to this Salesforce record was found in SharePoint.“.
Fixed an issue not showing all metadata values during search.
Fixed an issue that did not show a file icon if the file type was unknown.
Fixed an issue where some special characters were not being filtered.
Fixed spelling errors.
v3.0 Digital Experience
...
Config Changes
Reordered configuration steps in a more logical way.
Added the functionality to directly assign the Filenize Admin permission set to the current user if no assignments have been made yet.
Added more filters in the user status screen.
Added the option to assign/remove licenses and permission sets directly in the user status screen.
Added the option to export the current user status list to CSV.
Added a direct link to the Authentication Settings for an External System in the user status screen.
Updated the new SharePoint Instance prompt to present clickable links to all sites, subsites, document libraries and improved the search tool.
Fixed an issue with the open and close indicator for certain sections.
Fixed an issue when an error in a selector would not indicate an error on the section itself.
Fixed an issue that was triggering the permission check to many times per SharePoint instance.
...