Frequently Asked Questions

Owned by Henk-Jan van der Bijl
Last updated: Jan 16, 2024 by Daniël Loriaux
4 min read

Search

 

Table of Contents

 

When users use the login button, they only see a blank page.

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 address this issue, you need to create a new permission set or edit the user’s profile. Follow the instructions below:

For Legacy Named Credentials:

  1. Open Named Credential Access.

  2. Add your named credential to the Enabled Named Credentials column.

For New Named Credentials:

  1. Open External Credential Principle Access.

  2. Add your principle to the Enabled External Credential Principals column.

 Users don’t see Authentication Settings for External Users under their personal settings

Salesforce hides the menu item if the user lacks access to any named credential within the organization. To address this, create a new permission set or edit the user’s profile with the following steps:

For Legacy Named Credentials:

  1. Open Named Credential Access.

  2. Add your named credential to the Enabled Named Credentials column.

For New Named Credentials:

  1. Open External Credential Principle Access.

  2. Add your principle to the Enabled External Credential Principals column.

Users get an error during autentication “We can't log you in because of an authentication error“

Not applicable for Legacy Named Credentials

Non-administrators require read access to the External Credentials object in addition to the specific External Credentials Principle Access; otherwise, they will encounter an authentication error during login, which states, "We can't log you in because of an authentication error. For help, contact your Salesforce administrator." You can grant read access by:

  1. Navigating to your permission set (or profile) in Salesforce Setup.

  2. Accessing "Object Settings."

  3. Selecting "User External Credentials."

  4. Choosing the "Read" permission and saving the changes.

As an admin i don’t see my sites or subsites when configuring my SharePoint instance

This can be due to a couple of reasons:

  1. Your Named Credential URL is directly targeting your site or subsite. Ensure the URL ends with http://sharepoint.com.

  2. You may not have read permission on the site or subsite. Ensure your SharePoint admin has provided you with the necessary access rights.

  3. If you have recently been granted read permission, the method to display available sites and subsites is indexed by SharePoint. SharePoint refreshes its indexes every couple of minutes to an hour, and we do not have control over this process.

The workaround is to fill in the site or subsite in the search field and click on "Use" when done. The value can be found in the URL when visiting SharePoint Online, for example, .../mycompany.sharepoint.com/sites/SITE/SUBSITE/...

As a final note, it is important to configure Filenize with a user that has full control rights in SharePoint to avoid further permission issues.

As a user im not able to see a parent folder even though i have access to a subfolder

This is how SharePoint operates. A user retains access when directly accessing a subfolder but cannot navigate through the hierarchy from the parent folder to the subfolder. Filenize cannot alter the standard behavior of SharePoint. However, in Filenize, you have the option to pin the subfolder, allowing users to be directly directed to the specific folder they have access to.

Does Filenize use any middleware or additional endpoints outside of Microsoft?

Filenize directly communicates with the SharePoint API customized by the admin without utilizing a middle layer. During the installation of an app containing additional endpoints from AppExchange, users are always prompted to acknowledge potential risks. Filenize, however, only uses the endpoints provided by Microsoft to have access to Microsoft visual icons, which are:

 “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 )

For detailed instructions on setting up the connection between Salesforce and SharePoint, refer to the documentation at 3. Configure. The connection is established using Salesforce Named Credentials, ensuring control.

It's essential to add the following domains to the Named Credential:

As a user I’m not able to create a folder hierarchy where the total path is longer than 400 characters

The complete decoded file path, encompassing both the folder path and file name, must not exceed 400 characters for SharePoint. This limit is applicable to the combined length of the folder path and file name after decoding, as per SharePoint service descriptions (https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits).

As a user I occasionally get an 503 error

The HTTP status code 503 indicates that the SharePoint service is currently not prepared to process the request. This is commonly attributed to SharePoint experiencing more temporary load spikes than anticipated. While Filenize does display the error in the user interface, it automatically attempts the process again when utilizing Filenize invocable actions for automation.

After an update, I am encountering unexpected behavior

It’s possible that Filenize encounters difficulties in loading resources, displaying components, and may be deficient in providing error feedback after an update. This issue is attributed to Salesforce caching, and it may require a few additional minutes or refreshes before the product resumes functioning as expected. This is particularly noticeable in the 3.0 update, which involved a comprehensive overhaul of coding and UI changes.

I get the “an unknown error occurred“ message when doing x

This error occasionally occurs when using Filenize and is a specific SharePoint error associated with a 500 Internal Server Error. Typically, this error is short-lived, and Filenize will resume normal operation after a few minutes.

Occurred in the past:

  • Microsoft.Office.Server.Search.REST.SearchServiceException

Screenshot 2024-01-16 at 00.05.02.png
Example 500 error