› AutoStore › Route Components › SharePoint › Restrictions and limitations

Restrictions and limitations

  • The component is designed for work with the following versions of Microsoft SharePoint servers:
    • Microsoft SharePoint 2013 Server
    • Microsoft SharePoint 2016 Server
    • SharePoint Online (Office 365) Service
    • Microsoft SharePoint 2019 Server
  • When the AutoStore Add-on services connection method is used, the component can upload files by using two different methods:
    • Upload with buffering in the memory of the workflow server host machine. In this case, the size of the sent document is limited by available virtual memory on this computer.
    • Streaming upload. This method is used automatically if anonymous access is allowed to the following file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\_nsi\NsiUploader.aspx on the SharePoint server host machine.

      In order to allow the anonymous access, in the IIS settings select a desired site, select the _vti_bin/_nsi folder, open Authentication, and set Enable status for Anonymous Authentication.

    Use the most appropriate method for file uploading.

  • To work with this component, the user should have at least the 'Contribute' permission level for the specified folder, list, or document library.
  • To use impersonation, the user specified in the User name field should be a site collection administrator. With this option on, the documents and list items will be saved with the permissions of the impersonator.
  • If you use the Native Services connection method, then the component uses Client Side Object Model to access the server. These methods have the following special restrictions:
    • On the General tab, the Server log file option is disabled.
    • The component should be able to successfully transfer files up to 200 MB in size, but not more.
    • The site list can be got only for the specified site collection.
  • If you use the AutoStore Add-on Services connection method, on the General tab, the Impersonate option is disabled for SharePoint 2013, and later versions.
  • The component supports only the integrated Windows authentication and Forms-based authentication methods.

    The integrated Windows authentication methods rely on IIS authentication for SharePoint Web applications; the methods are NTLM or Kerberos (IIS Windows Authentication). IIS settings should be checked after the Web application is created: the Windows authentication method should be enabled.

    The Forms-based authentication methods rely on IIS authentication for Claims-based SharePoint web applications. IIS settings should be checked after the web application is created: the Forms-based authentication method should be enabled.

  • When using multiple level metadata, the hierarchy will be displayed on the device panel as a list. However, the tree view will not be displayed. The full hierarchical path is displayed to make the selection of the right metadata easier.
  • The Native Services connection mode supports only SharePoint 2013 Workflow.
  • For a proper operation of the component, Windows Identity Foundation (WIF) for .NET Framework 3.5 version should be installed on the machine, where workflow server is running.
  • The component is not able to retrieve and show more folders than the number specified in the List View Threshold field in the General settings of a web application on the SharePoint site. By default, this number is 5000.
    You can check the number specified for the selected web application by the following path: Central Administration >> Application Management >> Manage Web Application >> web_application >> General Settings >> Resource Throttling >> List View Threshold, where web_application is the name of a web application on the SharePoint site, for which you want to check the threshold.
  • Use of External Data fields has its additional number of restrictions that can be found in External Data field restrictions.
  • This component requires Token Vault to be installed and configured.