Understanding Flow Owners, Connections, Service Accounts, and Application Users The Four People Behind Every Flow Imagine a warehouse. Power Platform works the same way. Identity 1 - The Triggering User This is the person or system that starts the journey. Examples: A user updates a Case. A customer submits a form. An email arrives. A … Continue reading Who Actually Pays for the Request?
Opening Hook Imagine a customer raises a support ticket. "Our Power Automate flow is suddenly slow." As developers, our instinct is usually to open the flow designer. Sometimes one of those fixes works. Most of the time... We are fixing the wrong thing. Because we don't actually understand what happens after a flow is triggered. … Continue reading The Journey of a Single Request
Every few months I see another discussion where someone says: "Dataverse API limit is 6000." "No, it's 40,000 requests." "Actually it's 250,000." "Power Automate allows 500,000." Everyone sounds correct. Yet everyone is talking about a completely different limit. That is exactly why Power Platform limits are so confusing. Microsoft hasn't created one limit. They have … Continue reading There Is No Such Thing as “The Power Platform API Limit”
There is a quiet tax on most Power Automate flows: unnecessary loops. You retrieve 500 items from SharePoint. You need 12 of them. So you loop through all 500, checking a condition on each one, building a new array one item at a time. The flow works. It's also doing 488 units of work it … Continue reading Power Automate Data Operations What They Actually Do and When to Use Each One
Here's a scenario that plays out on almost every Power Platform project. You have three approval workflows: one for project proposals, one for leave requests, one for expense submissions. Each one needs to look up the list of approvers from a SharePoint group. So you build that lookup logic into the first flow, then copy … Continue reading Stop Copying Logic Across Flows. Use Child Flows
Power Automate gives every action a default name the moment you drop it onto the canvas. "Apply to each", "Condition", "Send an email (V2)". Then you move on, wire up the logic, and ship the flow. Six months later, someone maybe you, maybe a colleague opens it for the first time. They see twelve nested … Continue reading Stop Naming Your Flow Actions “Scope” and “Apply to Each”
So far in this series, we’ve explored how to initiate and automate bulk deletions in Dataverse, and how to protect critical records through retention. But how do you know your deletion job actually worked? In Part 4, we break down the tools and methods to track, monitor, and troubleshoot Bulk Delete operations. 1. Meet the … Continue reading Mastering Dataverse Bulk Delete – Track, Audit, and Debug Your Bulk Deletion Jobs
We have covered the what and how of bulk deletion in Dataverse. But not all data is disposable. In Part 3 of this series, we’ll explore when not to delete, how to manage retained records, and strategies for compliance-friendly cleanup that balances performance with governance. Understanding Retained Data For example: In healthcare, patient records must … Continue reading Mastering Dataverse Bulk Delete -Long-Term Retained Data and When Not to Delete
In Part 1 of this series, we explored the fundamentals of using the Bulk Delete feature in Dataverse to purge stale records at scale. In this part, we focus on how to schedule, automate, and monitor these jobs for ongoing success. Scheduling Bulk Delete Jobs Dataverse lets you schedule bulk delete jobs using the UI … Continue reading Mastering Dataverse Bulk Delete – Automating and Monitoring Your Cleanup Jobs
As enterprise applications grow, so does the data they collect. Test records, outdated leads, or inactive cases can clutter your system, slow performance, and inflate storage costs. Microsoft Dataverse offers a powerful yet underutilized feature to address this: Bulk Delete. In this first part of our Bulk Delete series, we explore how to use this … Continue reading Mastering Dataverse Bulk Delete – Simplifying Data Cleanup
