Tag archive
One git repo for all Power Platform governance: naming standards, review checklists, flow inventory, and AI review reports. Version-controlled.
Build a weekly Power Automate governance digest that emails new flows, broken flows, orphans, and policy violations to your platform team automatically.
Separate Power Automate notification flows from business logic. One rule: notification flows read Dataverse and send email, never write back. The notification layer becomes disposable without business risk.
Entity-area tags turn a flat list of Power Automate flows into a navigable architecture. A naming system that maps to ADO, source control, and AI agent batches.
I recently built a complete IT ticket management system in Power Apps — 9 screens, role-based access,...
FetchXML in Power Automate handles temporal queries, linked entity joins, and IN filters that OData $filter cannot. Patterns for notification flows.
Dealing with multiple Excel or CSV files is a common task in business. Whether it is sales reports...
Designer-first Power Automate is opaque to source control and AI. Spec-first development makes flow generation reviewable, diff-able, and parallelizable.
A connected methodology for building Power Automate solutions: spec-first authoring, tag-based architecture, notification separation, FetchXML over OData, and programmatic solution packaging.
How a precise markdown spec, tag-based architecture, and parallel AI agents turn a batch of notification flows into a clean Dataverse solution import. Pattern walkthrough.
https://meetlr.com/site/bluelockfullstorythai https://meetlr.com/site/bluelockthailandfhd https://mee...
https://wrapsenators.ca/articles/article-best-wrap-colors-2026