Table of Contents
Some users do not automatically have access to the named credential that was created, as it is not included in the Filenize User or Admin permission set. To resolve this, you need to create a new permission set or edit the user’s profile, edit it:
Legacy: open Named Credential Access, and add your named credential to the Enabled Named Credentials column.
New Named Credentials: open External Credential Principle Access, and add your principle to the Enabled External Credential Principals column.
Salesforce hides the menu item if the user does not have access to any named credential that exists in the org. This can be resolved using the steps described in 10.1
This can be due to a couple of reasons :
Your Named Credential url is directly targeting your site or subsite. Make sure the url ends with http://sharepoint.com
You don’t have read permission on the site or subsite. Make sure your SharePoint admin has provided you the minimal access rights
You have read permission but was granted recently. The method to show the available sites and subsites is done by a specific method which is indexed by SharePoint. SharePoint refreshes it indexes every couple of minutes / to an hour. We don’t have any control over this.
The workaround is to fill in the site or subsite in the Manual field and click on Use when done. The value can be found in the url when visiting SharePoint Online. i.e. …/mycompany.sharepoint.com/sites/SITE/SUBSITE/…
This is SharePoint’s way of working. A user still has access when going directly to the subfolder, but is not able to browse through the hierarchy from the parent folder to the subfolder. Filenize is not able to change the standard behaviour of SharePoint. In Filenize you would be able to pin the subfolder, so users are directly routed to the correct folder they have access to.
Filenize doesn’t use a middlelayer, it’s directly communicating with the SharePoint API customised by the admin itself. When installing an app that contains additional endpoints from the AppExchange, you get prompted during the installation to notify you about the potential risk. Filenize does not have any additional endpoints and you won’t get prompted as such.
“If the package contains a remote site setting, you must approve access to websites outside of Salesforce. The dialog box lists all the websites that the package communicates with. We recommend that a website uses SSL (secure sockets layer) for transmitting data. After you verify that the websites are safe, select Yes, grant access to these third-party websites and click Continue, or click Cancel to cancel the installation of the package.” (https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 )
There is documentation available on how to setup the connection between Salesforce and SharePoint. This is all done using Salesforce Named Credentials, so you have full control over the connection. (3. Connecting Salesforce with SharePoint )
The only domains Filenize uses are (which you need to add to the Named Credential yourself):
https://<your_tenant_name>.sharepoint.com (API resources)
https://login.microsoftonline.com/ (API Authentication)
The entire decoded file path, including the file name, can't contain more than 400 characters for SharePoint. The limit applies to the combination of the folder path and file name after decoding. (https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits)
503 indicates the SharePoint service isn't ready to handle the request. The common cause is that SharePoint is experiencing more temporary load spikes than expected. Unfortunately, this also impacts Filenize.