SharePoint OData Connector

26.4.0

New Features

  • In the Browse tab of the advanced configuration interface in NiFi Ingest, you can view the document metadata schema for items that exist in the repository. You can also view example document metadata that you could use when inserting an item into the repository.

Resolved Issues

  • When NTLM or Kerberos authentication was used for connecting to the SharePoint API, the connector would fail to retrieve data and log the error "No authentication method configured". This issue affected versions 26.3 and 26.2.

Notes

  • In this release there are changes to the document metadata produced by the connector. You might need to update downstream applications that rely on specific document metadata fields.

    Earlier releases Version 26.4

    Some metadata in a document representing a list:

    <FIELDNAME>Title</FIELDNAME>
<Title_FieldTypeKind>2</Title_FieldTypeKind>
<Title_Required>true</Title_Required>
<Title_Title>Title</Title_Title>

    Some metadata in a document representing a list item:

    <Title>My Document</Title>

    Some metadata in a document representing a list:

    <FIELD>
    <NAME>Title</NAME>
    <TITLE>Title</TITLE>
    <FIELDTYPE>
        <KIND>2</KIND>
        <NAME>Text</NAME>
    </FIELDTYPE>
    <REQUIRED>true</REQUIRED>
</FIELD>

    Some metadata in a document representing a list item:

    <FIELD>
    <NAME>Title</NAME>
    <TITLE>Title</TITLE>
    <FIELDTYPE>
        <KIND>2</KIND>
        <NAME>Text</NAME>
    </FIELDTYPE>
    <REQUIRED>true</REQUIRED>
    <VALUE>My Document</VALUE>
    <EDITVALUE>My Document</EDITVALUE>
</FIELD>
<FIELDVALUES>
    <Title>My Document</Title>
</FIELDVALUES>

    EDITVALUE is usually equal to VALUE but in some cases is different, for example in lookup fields. Read-only fields have no EDITVALUE.

    The FIELDVALUES element contains a simple name to value mapping, for all fields.

26.3.0

There were no new features or resolved issues in this release.

26.2.0

There were no new features or resolved issues in this release.

26.1.0

There were no new features or resolved issues in this release.

25.4.0

There were no new features or resolved issues in this release.

25.3.0

There were no new features or resolved issues in this release.

25.2.0

There were no new features or resolved issues in this release.

25.1.0

There were no new features or resolved issues in this release.

24.4.0

New Features

There were no new features in this release.

Resolved Issues

  • The connector was not able to perform incremental synchronize with on-premise SharePoint installations when there were multiple site collections and ChangesFromContentDatabase=false, because it would fail to obtain the change log.

24.3.0

There were no new features or resolved issues in this release.

24.2.0

There were no new features or resolved issues in this release.

24.1.0

There were no new features or resolved issues in this release.

23.4.0

New Features

  • The connector can handle the "Everyone except external users" group when generating document ACLs for mapped security. To use this feature, you must also upgrade your OmniGroupServer installation so that you are using the latest version of the Azure Active Directory plugin.
  • When generating document ACLs for mapped security, the connector can handle additional types of claim that contain SIDs - specifically the claim types ) and *.

Resolved Issues

There were no resolved issues in this release.

23.3.0

New Features

  • You can configure the connector to generate metadata-only documents and ignore binary files. The connector has a new configuration parameter named SynchronizeMetadataOnly. The collect and view actions support the new action parameter MetadataOnly.

Resolved Issues

There were no resolved issues in this release.

23.2.0

New Features

  • Improved performance when retrieving information about site collections. Additionally, the connector does not fetch the list of site collections again until a new synchronize task begins (if a task is stopped before it finishes, the connector does not fetch the list of site collections again when the task is resumed).
  • The connector has improved handling for rate limiting (when it receives an HTTP 429 "Too Many Requests" response code).

Resolved Issues

There were no resolved issues in this release.