Skip to main content
Sign in

Missing fetchACLs option and parsing behavior in SharePoint V2 optimized connector

  • Updated

Issue

Users working with the SharePoint V2 optimized connector may encounter one or more of the following issues:

  • The fetchACLs option is not visible in the connector UI.

  • Disabling async parsing causes ingestion to fail or produce errors.

  • The connector lacks support for ingesting SharePoint items by GUID when URLs are not available.

 

Diagnosis

These issues may arise when using specific versions of the SharePoint V2 optimized connector or when certain configurations are applied. Confirm the following:

  • You are using a version of the connector that includes the fetchACLs toggle (see Resolution).

  • Async parsing has been disabled in environments where the legacy Tika parser is deprecated.

  • You are attempting to crawl SharePoint content using GUIDs only, without corresponding SharePoint item URLs.

 

Environment

  • Fusion 5.9.14

  • SharePoint V2 optimized connector

  • Amazon EKS (Elastic Kubernetes Service)

 

Cause

  • The fetchACLs toggle was removed from the UI in connector version 2.1.0.

  • The deprecated Tika parser may produce errors when async parsing is disabled.

  • SharePoint item GUIDs cannot be directly resolved by the connector without a conversion step.

 

Resolution

Use version 1.6.1 to access the fetchACLs option

The fetchACLs setting allows users to prevent ACL documents from being indexed. This option was present in version 1.6.1 but is not available in later releases such as 2.1.0.

To access this feature:

  • Download version 1.6.1 of the SharePoint optimized connector from the Lucidworks plugin portal.

  • Upload the connector to Fusion and check the Advanced tab in the data source configuration UI.

  • Locate the Fetch ACLs toggle under Moderation status filter.

Note: If your deployment does not use SharePoint ACLs, disabling fetchACLs can prevent unwanted ACL documents from being indexed.

 

Ensure async parsing is enabled

Async parsing is required for the SharePoint V2 optimized connector to function reliably. The legacy Tika parser, which was used in prior versions, is deprecated and may be removed in future Fusion releases.

Recommendations:

  • Keep async parsing enabled for optimal compatibility.

  • Avoid disabling this setting unless you have a specific alternative parsing strategy in place.

Note: Issues related to async parsing errors should be handled separately, as they may stem from parsing configuration or malformed content.

 

Workaround for indexing SharePoint items by GUID

The connector does not natively support ingesting SharePoint items by GUID alone. If you have a list of GUIDs and no corresponding URLs, follow these steps:

  1. Use the Microsoft Graph API or SharePoint REST API to resolve each GUID into a SharePoint webUrl.

  2. Add the resolved URLs to the Restrict to specific SharePoint items field in the connector configuration.

Note: This conversion step is required because the connector can only crawl resolvable SharePoint URLs.

Related articles

Powered by Zendesk