SharePoint (CMIS Connection Type)

From Grooper Wiki
(Redirected from SharePoint (CMIS Binding))

This article was migrated from an older version and has not been updated for the current version of Grooper.

This tag will be removed upon article review and update.

This article is about the current version of Grooper.

Note that some content may still need to be updated.

2025 20232.72

SharePoint is a CMIS Connection Type that connects Grooper to Microsoft SharePoint, providing access to content stored in "document libraries" and "picture libraries" for import and export operations.

Connectivity is compatible with both online and on-premises SharePoint deployments via the SharePoint REST API.


About

Microsoft SharePoint is a web-based collaborative platform that integrates with Microsoft Office.  It is primarily a document management and storage platform, but it is highly configurable and its implementation varies from company to company.  Grooper utilizes what SharePoint calls "Document Libraries" to import and export documents with property mappings.  When you create a Document Library in SharePoint, not only do you have access to standard document properties like "Created By" or "Content Stream Length", but you can add custom ones as well.  This allows Grooper to map fields from a data model onto documents within a Document Library.

Supported versions include SharePoint 2013 or higher.  However, for SharePoint 2013, connections must be made to the root site.  Connecting directly to a subsite is not supported.

BE AWARE!

When querying a SharePoint repository, the IN_FOLDER predicate is not supported. You must use the IN_TREE predicate to search for documents in Document Library's folder structure.

Also, be aware the IN_TREE search is recursive where IN_FOLDER is not. This means any subfolders will be queried as well as the targeted folder.

How To: Set Up a SharePoint Connection





How To: Set Up a Document Library in SharePoint

As mentioned earlier, Grooper connects to Document Libraries in SharePoint to map fields in a data model to properties of a Document Library.  First, we need to make a Document Library and set up its properties.

Go to your SharePoint site.  Using the left navigation column, click on "Site Contents"



From here, click on the "New" button next to the plus icon, and select "Document Library".  It will prompt you for a name and optional description.



You've created an empty document library.  You can see a few of the default properties, Name, Modified, and Modified By.  At the end of this line, you will see "Add Column" next to a plus sign.  Click this to add new properties.



This will give you a variety of types for your data elements.  For example, "Single line of text" would correlate to a simple string variable.



This brings up a new menu to name the column (or property), give it a description, alter the type (which will correspond to a similar type in Grooper), and assign a default value if desired.



The added property will appear as a new column.


Known Issues & Limitations

SharePoint CMISQL Query Limitations

The SharePoint connection binding does not support the IN_FOLDER predicate.

  • You must use the IN_TREE predicate instead when selecting a folder location to query.
  • Be aware the IN_TREE search is recursive where IN_FOLDER is not. This means any subfolders will be queried as well as the targeted folder.


The SharePoint connection binding has a hard limitation when it comes to querying larger repositories, with many thousands of folders and files.

  • There is currently a threshold limit of 5000 rows.
  • This means if a query has to scan more than 5000 items to return an item, SharePoint will return the following error:
    • "Internal Server Error (500): The attempted operation is prohibited because it exceeds the list view threshold."


See Also

For more information to use your CMIS Connection once its created, see the following articles: