A Power Automate flow description tells you what the flow is for. It does not tell you why the third action runs after every status, or why a lookup is bound by code instead of by GUID. Those answers usually live in the head of whoever built it, which is a poor place to keep
Power Automate Notes: Documenting a Flow Action by Action Read More »
Awaab’s Law measures damp and mould deadlines in working days. Ten working days to investigate, another five to make safe, three more for the written summary. Dataverse calculated columns cannot do working-day arithmetic, so none of those deadlines can be worked out until the platform knows which days do not count. That is why the
Using Claude Code to Build Power Platform, and to Teach It Read More »
GUIDs are great until they are not. A GUID gives every record a unique reference that is never duplicated, and it lets us find one specific record among hundreds of thousands. But there is a scenario where relying on one will catch you out. Imagine this. You’re developing a solution in a development environment. You
Alternate Keys in Dataverse: Stop Hardcoding GUIDs Read More »
I recently worked on a project to create a Canvas App that displays all tasks and projects at an organization in a gallery view. One seemingly simple requirement turned into an interesting learning experience: displaying who a record is assigned to. The Challenge: Accessing the Owner Field My first instinct was to use ThisItem.Owner in the gallery to
How to Display Record Owners in Power Apps Canvas Gallery (Without Trigger Loops) Read More »
