This post explores how Power Automate (cloud) child flows return structured responses to parent flows using a standard output contract. The contract explicitly distinguishes between successful executions, business exceptions, and system exceptions, ensuring the parent flow can make deterministic decisions based on outcome rather than raw failure states.
On a Windows 11 machine, I recently connected Power BI Desktop to both Azure SQL Edge and SQL Server 2019, hosted on Docker. By running these servers locally, you avoid connecting to the cloud and certain Azure hosting subscription charges, e.g. Pay-AS-You-Go, when...
If you are building Canvas Apps with screens that browse SharePoint Online Lists containing over 5000 items; you should be mindful of how you configure these Lists and the impact on Filter, Search, LookUp , Sort ( single columns only) and SortByColumns functions....
There are occasions, when you want to restart failed flow (Power Automate) runs or enabling (turning on) flows, after a solution deployment. You can do either of these tasks manually in the web browser or better still create repeatable scripts, combining PowerShell...
Want a better way to view the output in a Power Atomate trigger action such as SharePoint: when an item is created and easily determine a property value? This post will show how you can have nicely formatted JSON output with a simple extension in Edge Chromium. In...
This post covers a suggested naming standard that will help to aid consistency and maintainablity when working on Power Apps. If you adopt the suggested three character prefix, you limit how much you need to type but still be able to distingish each control. You...
Westerdale Solutions LTD
Design and deliver components of Power Platform solutions, focussing on:
The blog post lottery, discover something new today with a random post from any category
This post explores how Power Automate (cloud) child flows return structured responses to parent flows using a standard output contract. The contract explicitly distinguishes between successful executions, business exceptions, and system exceptions, ensuring the parent flow can make deterministic decisions based on outcome rather than raw failure states.
