Content Service Connector - Alfresco Federation Services - 3.2 - 3.2 - Ready - Alfresco - external - Alfresco/Alfresco-Federation-Services/3.2/Alfresco-Federation-Services/Configure/Connectors/Microsoft-Graph/Microsoft-Graph-SharePoint/Content-Service-Connector - 2025-03-04

Alfresco Federation Services

Platform
Alfresco
Product
Alfresco Federation Services
Release
3.2
License

Configuration

  • Tenant Name: The name of the tenant. All O365 SharePoint instances use the structure [tenant].sharepoint.com. We use this to construct urls and gather site IDs.
  • Site Name: The path to the target site as it would appear in the SharePoint url.
  • List Name: The name of the library, as seen on the sites’ sidebar.
  • SiteId: After configuring the connection the first time this can be populated using the REST APIs. See the Root Folder example below.

Examples

Document and folder ids will look like this.

01WNAC6ZYYYWDZOWH2DFH3LRHT7MWF5L2R

As SharePoint is actually backed by OneDrive, all the ids are actually OneDrive Ids as well.

Routing document

Following are simple examples of routing documents of different file types to different locations within your tenant.

These examples assume you are using the default override field names.

if(rd.getMimeType() === 'application/pdf'){
  rd.addSingleField('site','sites/Simflofy');
  rd.addSingleField('list','Documents');
}
if(rd.getMimeType() === 'text/plain'){
  rd.addSingleField('list','Test Lib')
}