Summary The Knowledge Agent can autofill metadata for files and generate SharePoint lists from content. By default it processes the first 20 files; you can select additional files and re-run Autofill to apply the same extraction over more items. How it looks Create the following autofill columns (suggested) Claim ID Policy number Claimant name Address (UK cities) Phone & email Claim type (motor, health, property, travel, accident) Incident date & location Claim description Claim amount (£) Report date Signature Autofill behaviour Initially, the agent applies autofill to the first 20 files only:

This post provides a PowerShell script to import synonyms (labels) into a SharePoint term set using the PnP.PowerShell module. The sample using PnP PowerShell to import a csv file (same format you would use for import via UI for a term set but with an additional column for Synonyms delimited by |) Prerequisites Install the PnP.PowerShell module (run as an admin): Install-Module PnP.PowerShell -Scope CurrentUser An Azure AD app or other authentication method with sufficient permissions to manage taxonomy/term store, or use interactive Connect-PnPOnline.

Introduction Tips working with document set. Document sets are basically folders in the background Column formatting to display folder name into the library Document set is a folder in the backend, hence could apply the following Json to see which document set a file has been moved to. { "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json", "elmType": "div", "txtContent": "=replace(replace(replace([$FileRef],[$FileLeafRef],''),'/sites/test/Shared Documents/',''),'/','')" } View to see all the document sets Limitations Nested document sets not allowed A file don’t belong to two document sets Advantages Apply metadata to files within the document set Manage as a logical grouping of files Do SharePoint document sets: when and why to use them covers usage and benefits of document sets.