To get all your broken connections in the Power Platform can be a challenge. In this post I will use flow to collect the broken connections.
In this post I will have a look at using a flow to collect the broken connections after someone contacted me today about the PowerShell solution that I wrote a while back.
At first I started building my flow and then I quite quickly ended up with the hated nested apply to each steps.
The better way is to create a flow that doesn’t use any nested apply to each steps like the one below:
Ok, you might want to schedule these flows on a daily basis or so and then send an email at the end, but that is a bit of detail that we can worry about later. In this post I want to focus on getting the failing connections only.
We all use multiple enviroments, don’t we? so I want to step through the different environments first. so after my intial trigger of the flow I will add a Get Environments action.
No need to bother with an apply to each here. Power Automate will add it automatically as we complete the configuration of the Get Connections action.
So just add the get connections and select name form the dynamic properties as shown below.
The next action is a select.
I’m going to use the following expressions in the above select.
Now we just need to filter the connected connections out and we have all the connections that are in trouble.
now all we need to do is collect the results from the filters and we will have a single array with all the failed connections from all environments.
Do you want to know who is in the office tomorrow or the day after?…
Why would you use Dataverse, if SharePoint lists gives you the option to avoid premium…
When you read items from a SharePoint list and you want to filter by calculated…
A few weeks ago I looked at calling flows from model driven apps. And for…
If you call Customer Voice still Forms Pro or not, have you ever looked into…