v1.6.1

Changelog

• 09666f7 Dept bump
• 21c9af8 Exclude hidden lists from rollup

v1.6.0

Changelog

• Content Types based rollup

Content Types based rollup allows to fetch data from multiple lists or document libraries based on the Content Type configuration.

All items based on the parent content type are fetched from all lists and subwebs below the context site URL.

# sharepoint.yml
# ...
spec:
  # A map of Content Types with the rollup configurations
  content_types:
    # Base Content Type name or ID (e.g. "0x0101009D1CB255D" must be in quotes)
    Task:
      # REST `$select` OData modificator, fields entity properties array
      select:
        - Title
        - AssignedTo/Title
      # REST `$expand` OData modificator, fields entity properties array
      expand:
        - AssignedTo
      # Optional, an alias for the table name
      # the name of the alias is prefixed with `rollup_`
      alias: "task"

v1.5.0

Changelog

• Fields mapping support

Selected fields for lists, document libraries and search selected properties now can be aliased to have custom names.

# sharepoint.yml
# ...
spec:
  lists:
    Lists/ListEntityName:
      select:
        - Title
        # Fields mapping via `->` arrow alias, when a specific field name is considered
        - EditorId -> editor

v1.4.1

Changelog

Fixes

• On-Demand auth failing open Chrome window

v1.4.0

Changelog

Features

• User Profile Service data
• Search queries data

User Profile Service data

User Profiles are fetched via Search API, so the search should be configured in the farm.

Search drived data source can be user only with user associated authentication strategies. E.g. it won't work with addin strategy.

# sharepoint.yml
# ...
spec:
  # Include `profiles` property to fetch user profiles
  # Object structure for extensibility (adding custom properties)
  profiles:
    enabled: true
    # Optional, an alias for the table name
    alias: "profile"

Search queries data

Search drived data source can be user only with user associated authentication strategies. E.g. it won't work with addin strategy.

# sharepoint.yml
# ...
spec:
  # A map of search queries
  search:
    # Query name (whatever you want to name a resulted table)
    # Should be unique within other compound aliases
    documents:
      # Required, search query text
      # https://learn.microsoft.com/en-us/sharepoint/dev/general-development/sharepoint-search-rest-api-overview#querytext-parameter
      query_text: "*"
      # Optional, the managed properties to return in the search results
      # https://learn.microsoft.com/en-us/sharepoint/dev/general-development/sharepoint-search-rest-api-overview#selectproperties
      # By defining the list of properties, you also tell the plugin
      # to have correcponding columns in the table
      select_properties:
        - Size
        - Title
        - ContentTypeId
        - IsDocument
        - FileType
        - DocId
        - SPWebUrl
        - SiteId
        - WebId
        - ListId
      # Optional, whether duplicate items are removed from the results
      # https://learn.microsoft.com/en-us/sharepoint/dev/general-development/sharepoint-search-rest-api-overview#trimduplicates
      trim_duplicates: true
    profiles:
      query_text: "*",
      trim_duplicates: false
      # The result source ID to use for executing the search query.
      # https://learn.microsoft.com/en-us/sharepoint/dev/general-development/sharepoint-search-rest-api-overview#sourceid
      source_id: "b09a7990-05ea-4af9-81ef-edfab16c4e31"

v1.3.0

Changelog

Features

• Added NTLM2 auth support
• Added On-Demand auth support

NTLM auth

For environments with NTLM where the default auth might not work: https://go.spflow.com/auth/strategies/alternative-ntlm

On-Demand Auth

On-Demand auth with popup windows for user credentials prompt: https://go.spflow.com/auth/strategies/on-demand

Allows easily connect to cookie based, SSO, environments with 2FA.

v1.2.0

Changelog

Features

• Managed Metadata support

To configure managed metadata fetching, you need to provide a term set ID (GUID) and an optional alias for the table name.

# sharepoint.yml
# ...
spec:
  # A map of MMD term sets IDs (GUIDs)
  mmd:
    # Term set ID
    8ed8c9ea-7052-4c1d-a4d7-b9c10bffea6f:
      # Optional, an alias for the table name
      # the name of the alias is prefixed with `mmd_`
      alias: "department"

v1.1.0

Changelog

Features

• Lists filtering support
• Auth spec validation

v1.0.0

Changelog

Features

• SharePoint Online and On-Premise support
• Lists sync configuration