Archives

SSRS and Word templates are the two print paths Dataverse already gives you, and both fail the same load test.

Code Apps feel like plain React until five undocumented runtime quirks turn a working local build into a blank screen in the host.

Microsoft Graph's convert-to-PDF returns a 302, not a PDF — and if your HttpClient follows redirects, it leaks your bearer token.

Anyone can build a clock-in button. The real engineering is watching active shifts as they run, so a missed break is a flag today, not a payroll surprise in two weeks.

A product I built shared one Postgres database with a third-party AI service — and inherited every table that service forgot to lock.

A legal-tech tool that reads a contract and computes late-payment interest — where the AI extracts every figure and a deterministic engine, not the model, does the maths.

The Power Platform connector caps your file size, and base64-ing bytes through a flow inflates them a third until it falls over. Here's the SAS-and-stream pattern that moves the file out of the connector entirely.

Most people think Power Platform means canvas apps. It doesn't. Here's how a fleet of full React apps ran natively on the platform against Dataverse — and the read/write split that made it work.

Going fully client-side removed an Azure Function and a whole class of failure. Then the Power Apps SDK quietly ate every file I tried to read back.

Nearly every typed SharePoint connector action broke on the way to three million files. What broke, why, and the REST passthrough, retry policy, and business-key join that fixed it.

Copilot Studio is a suspension bridge. Most of your requirements are streams — and a form plus a flow crosses them just fine.