LowCodeStacks™
Sign in

Guides · 119

What are you trying to do?

Fix a problem

68The error or symptom in front of you, and the fix.

Choose a tool

11Decide before you build.

Design patterns

12Structures that hold up as things grow.
  • Identity & security

    Azure access in one picture: Entra ID, RBAC and managed identities

    Azure access has three parts that people mix up: Entra ID says who you are, Azure RBAC says what you may do and at what scope, and managed identities let your services do it without secrets. One picture, the two kinds of role, the two planes, and the five places access goes wrong.

  • Azure + Power Platform

    When your Power Platform solution needs Azure: the services worth knowing

    Power Platform and Azure integration on one page: which Azure service to reach for when an app, flow or agent outgrows the platform, from custom connectors and Key Vault to private networks, events, search, monitoring, billing and deployment.

  • Copilot Studio

    Grounding an agent safely: what to connect and what to keep out

    A Copilot Studio agent doesn't create new access, but it makes existing access easy to use. Oversharing that nobody noticed in SharePoint becomes an answer anyone can ask for. A pattern for connecting knowledge and tools without leaking what shouldn't leak.

  • Dataverse

    Security roles, business units and teams without the tangle

    Dataverse security is powerful and easy to get into a knot. A pattern for roles, business units and teams that gives each person exactly the access they need, stays readable as the organisation grows, and avoids the one mistake you can't undo.

  • Power Apps

    Named formulas and components: a structure that scales

    Most slow, fragile Power Apps canvas apps share one cause: everything lives in App.OnStart and copied controls. Here is a structure built on named formulas, user-defined functions and a component library.

  • Power Automate

    Child flows that fail well: inputs, results, errors and connections

    Child flow error handling that works: split a big flow without losing track of failures. Set up the child so it always reports back, let the parent decide what to do, avoid the 'child workflows only support embedded connections' error, and license it correctly.

  • Power Automate

    Reminder emails for items due soon: a daily flow that gets dates right

    Send a reminder a set number of days before a SharePoint due date. A daily scheduled flow that works in your time zone, filters the list efficiently, avoids double-sending, and can send one digest per person instead of a flood of emails.

  • Power Automate

    Try, catch and finally: error handling with scopes

    In Power Automate, a failed action just stops the flow by default, and the owner may never hear about it. The try-catch-finally pattern with scopes makes every failure visible, logged and handled.

  • Power Automate

    UI elements that survive changes: robust selectors for desktop flows

    UI element not found in a Power Automate desktop flow after an app update, a new window title or a different screen? Make selectors that keep working: find what changes, remove the dynamic parts, add fallback selectors, wait for the screen, and repair quickly when it does break.

  • Power BI

    Dynamic row-level security with USERPRINCIPALNAME that actually filters

    Dynamic row-level security in Power BI: one role, and every user sees only their rows. Build the user-mapping table, put the filter on the right table, avoid the bidirectional trap, assign people in the service, and test it properly, including guest users and why 'Test as role' can fool you.

  • Power BI

    One semantic model, many reports

    When every report brings its own copy of the data, every report defines revenue a little differently. One shared semantic model for multiple reports fixes that. Here is how to set one up, let people build on it, and keep it trustworthy.

  • Power Pages

    Web roles and table permissions: securing portal data

    On a Power Pages site, Dataverse security roles don't protect your data; web roles and table permissions do. A pattern for deciding who can see and change which records, and the shortcuts that quietly expose everything.

Measure

6Know whether it's working.

Quick reference

22Error codes, limits and cheat sheets to keep open.