Power Automate can create a SharePoint site end-to-end via the SPSiteManager/Create REST endpoint — no PowerShell, no admin center click-through. Useful for project sites, department portals, or onboarding sites that get created the same way every time. In this post: Prerequisites · The flow structure · Step-by-step walkthrough · Testing the flow · Checking before […]
How to Create a SharePoint Site Using Power Automate Read More »
Worth leading with directly, since it changes which flow pattern is actually worth building: Power Automate’s SharePoint connector has a dedicated Copy file action that copies server-side, without the file’s content ever passing through the flow — a meaningfully better default than the “Get file content” + “Create file” two-step pattern for most straightforward copies.
How to Copy Files from One Site to Another Using Power Automate Read More »
Worth leading with directly, since it changes what this post can actually recommend: `.getAll()` was removed entirely in PnPjs v4, the current major version as of 2026. The replacement isn’t a renamed method — it’s a genuinely different pattern, the same async-iterator (`for await…of`) approach covered from the JavaScript-fundamentals side in Does “for…of” loop wait
PnPJs .getAll() Function to get all list items Explained Read More »
PnP (Patterns and Practices) is the umbrella for several separate tools that speed up SharePoint Framework development — PnPjs for calling SharePoint from code, PnP PowerShell for admin/automation tasks, and a library of reusable React controls for SPFx web parts. This post covers what each actually does, where the real limitations are, and two places
Worth a direct correction before anything else: a `for…of` loop does wait for an `await` inside it — each iteration pauses until the awaited promise resolves before the loop advances to the next one. That’s the opposite of what a stub answer to this question sometimes claims, and it’s easy to get backwards since the
Does “for…of” loop wait for async awaits in JavaScript? Read More »
Creating many list items in one call means the same SharePoint REST `$batch` endpoint covered from the PnPjs side in SharePoint Data Handling with PnP Batching Queries — worth reading there for the wire-format details and the real 100-request cap, both of which apply here too. This post stays on the raw `fetch`-based approach specifically,
Creating Multiple SharePoint List Items Using SharePoint REST API Read More »
Worth leading with directly, since it’s the biggest recent change to this topic: JavaScript now has a native, built-in replacement for the notoriously bad `Date` object. The `Temporal` API reached TC39 Stage 4 (officially part of the language spec) in March 2026 and is already shipping in Chrome, Firefox, and Edge — immutable, timezone-aware, and
Store and Display Dates Properly in JavaScript Read More »
The SharePoint REST API is organized entirely around one root path — {site-url}/_api/ — with everything else (lists, files, users, search) hanging off web, site, or a dedicated service beneath it. Here’s a reference list of the endpoints you’ll actually reach for, plus a working example calling one from plain JavaScript. In this post: Site
Exploring SharePoint REST API Endpoints Read More »
Plain fetch() or XMLHttpRequest work fine for hitting SharePoint’s REST API — the part that’s actually SharePoint-specific isn’t the HTTP call itself, it’s the headers: an Accept header SharePoint’s OData implementation expects, and a request digest token required on anything that isn’t a GET. In this post: A GET request: fetching list items · A
How to Send an HTTP Request in SharePoint via JavaScript Read More »
SPFx (SharePoint Framework) is Microsoft’s current framework for building client-side web parts and extensions with TypeScript and React. The basic shape of getting started hasn’t changed, but two real pieces of the toolchain have — the build tooling and the way you test locally — and a lot of “getting started” guides still show the
Start your SharePoint with SPFX Read More »
