A SharePoint Content Type is a reusable bundle of columns, settings, and (optionally) a document template that you define once and apply across multiple libraries, instead of manually adding the same “Invoice Number,” “Due Date,” and “Amount” columns to every library that handles invoices. In this post: Why use content types · Creating one with
SharePoint Content Types: The Good, The Bad, and The Ugly Read More »
Updating a thousand SharePoint list items one request at a time is slow and burns through API throttling limits fast. PnPjs batching bundles multiple operations into a single HTTP call instead. Here’s the syntax for both the older and current versions of the library, and the real limit worth knowing before you rely on it.
SharePoint Data Handling with PnP Batching Queries Read More »
Moving SharePoint content between tenants (for a merger, acquisition, or restructuring) has more options than it used to, ranging from a manual drag-and-drop to a native Microsoft-managed pipeline. What you keep (permissions, version history, workflows) varies a lot between them, which is the real deciding factor, not just price. In this post: Native Microsoft 365
How to Migrate SharePoint Online Content to Another Tenant: All Available Options Read More »
