SharePoint

A SharePoint list rarely stays exactly the way it was when an integration was written. A friendly column label gets renamed, a field is replaced, or a team moves from SharePoint REST to Microsoft Graph. The frustrating result is that a harmless content change can break a public directory, dashboard, or scheduled job. The problem: …

A SharePoint integration can return HTTP 200 and still be completely wrong. That is one of the most annoying failures to troubleshoot: the request succeeded, but the list is empty, the wrong site was resolved, or Graph returned a different field shape than expected. The problem: “successful” responses that contain bad data Imagine a directory …

The fastest way to turn a temporary Microsoft 365 problem into a public incident is to overwrite yesterday’s valid file with today’s empty one. I have seen jobs authenticate correctly, receive valid JSON, and still produce unusable output because a list was renamed, permissions changed, or an upstream query returned zero rows. The problem: the …

AI can produce a SharePoint script that looks convincing in seconds. The problem is that “looks convincing” is dangerous around Microsoft Graph permissions, internal field names, account identifiers, and production data. The best use of AI is not asking it to build the whole solution blindly. It is using it to expose the cases I …

One Microsoft 365 person can arrive in three different shapes depending on whether the data came from SharePoint REST, Microsoft Graph, or an older custom endpoint. If that inconsistency leaks into the front end, every template fills up with “if Graph, do this; if REST, do that.” The problem: the same email has three paths …

SharePoint will happily store an email address with a trailing space, a URL without https://, or a Banner ID copied with an invisible character. The list looks fine to a person, but the integration cannot match accounts reliably. The problem: “almost correct” data Every value is understandable to a human. Two of them will fail …

A scheduled SharePoint job runs twice after a timeout. Now the calendar has duplicate meetings, the directory has duplicate employees, or the document library contains two copies with slightly different names. The job technically “worked” both times. The problem: creation is easier than identity Developers often search by title before creating an item. Titles are …

A SharePoint calendar event looks correct in SharePoint but appears one day early in Outlook, spans two days in Google Calendar, or duplicates every time the feed refreshes. ICS is a simple text format with several sharp edges. The problem: all-day events are not midnight meetings If an all-day event is exported as midnight in …

PHP can talk to Microsoft 365 just fine. The annoying part is that a quick proof of concept often mixes authentication, Graph URLs, SharePoint internal field names, and presentation code in one file. It works—until a token expires or one column changes. The problem: the page knows everything That URL returns list items, but Graph …

A public dashboard needs data from SharePoint Online. The obvious solution is to call Microsoft Graph directly from JavaScript—but that immediately creates a bigger problem: where do the credentials go, and how much of the tenant should the browser understand? The problem: a public browser is the wrong trust boundary The browser should not know …