...
Open External Credential Principle Access.
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“
| Info |
|---|
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:
Navigating to your permission set (or profile) in Salesforce Setup.
Accessing "Object Settings."
Selecting "User External Credentials."
Choosing the "Read" permission and saving the changes.
As an admin i don’t see my sites or subsites when configuring my SharePoint instance
...
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:
Learn more about these endpoints here: https://learn.microsoft.com/en-gb/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide&redirectSourcePath=%252fen-us%252farticle%252fOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2
“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. Connecting Salesforce with SharePointConfigure. The connection is established using Salesforce Named Credentials, ensuring control.
...
As a user I’m not able to create a folder hierarchy where the total path is longer than 400 characters
The entire complete decoded file path, including encompassing both the folder path and file name, can't contain more than must not exceed 400 characters for SharePoint. The This limit applies is applicable to the combination 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 isn't ready to handle is currently not prepared to process the request. The common cause is that SharePoint is This is commonly attributed to SharePoint experiencing more temporary load spikes than expected. Unfortunately, this also impacts Filenize. 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
...