20 articles
Power Apps Component Framework lets you build React-based custom controls for model-driven forms and views. Most of the time, you shouldn't. Here's when PCF is the right answer — and what the tooling docs don't warn you about.
Subgrids show related records directly on a form. Here's how to add them, choose the right relationship, filter the records, enable inline editing, and set up a New button that pre-fills the parent lookup.
Licensing isn't a procurement problem — it's an architecture decision. Here's the mental model every solution architect needs before starting a Power Platform project, with real scenarios and a pre-project checklist.
A parent dropdown for Country, a child dropdown for City that only shows cities in the selected country. Here's the pattern, the delegation-safe version, and the reset behavior that catches everyone.
A senior D365 developer's guide to JavaScript in model-driven apps — form events, Xrm.WebApi, field manipulation, async OnSave, debugging, and the patterns you'll actually use in production.
Calling a flow from a canvas app is straightforward once you get the trigger right. Here's how to set up inputs, return data to the app, and fix the issues that come up when the two don't talk to each other.
A collection of the most common Power Platform developer questions — from delegation errors to Dataverse throttling — with answers that go beyond the official docs.
The yellow triangle isn't just a warning — it means your app is silently returning incomplete data. Here's the complete guide to delegation limits, which functions are safe, and five workarounds ranked by reliability.
Lookups are how Dataverse tables relate to each other, and they're the column type that causes the most confusion in Power Apps. Here's how to set them up and work with them in canvas apps.
The debate around low-code platforms usually generates more heat than light. Here's a grounded take on when Power Platform is genuinely the right tool — and when it isn't.
Step-by-step guide to adding a custom command bar button to a Dataverse table in a model-driven app — using the modern Command Designer, no XML editing required.
Blank values in Power Apps cause unexpected errors, wrong comparisons, and broken lookups. Here's how to check for them, handle them safely, and stop your formulas from silently failing.
Business rules are the fastest way to control field visibility and editability on model-driven forms without writing code. Here's how to set them up and avoid the common traps.
The Patch function is how you create and update records in canvas apps. Here's the syntax for every column type, including lookups and choices, plus fixes for the errors you'll definitely hit.
How to create, configure, and use environment variables across Power Apps, Power Automate, and plugins — plus the deployment strategy that keeps things clean.
The User() function gets you started, but most real scenarios need more. Here's how to get the current user's details from Dataverse, including Business Unit, Team membership, and security role.
Both can validate data, set field values, and show or hide form elements. But they work very differently under the hood. Here's a clear guide to when to use each one.
Power Apps has three ways to store data in memory: global variables, context variables, and collections. Here's when to use each one and the mistakes that trip up beginners.
A practical guide to filtering lookup fields in model-driven apps using addPreSearch, addCustomFilter, and the no-code Related Records Filtering option.
Every Power Apps project starts with this question. Here's a framework for making the right call — and the cases where the answer is both.