Power Platform Community Forum Thread Details

I've actually found one use for the horrid New Designer.

I have a number of duplicate flows (created using Save As on a master flow) that build Planner Buckets. This flow has eight 'For Each' actions. In each of them, there is a condition and an action for IF Yes and for IF No. I'm now going through each of them and assigning them to the proper Groups and Planner Buckets.

Opening all of these in the Good Designer causes everything to come to a stall. Interestingly, I can fully expand all these actions in New Designer and breeze through the adjustments - not as fast as when Good Designer doesn't stall, but usable.

Now, just this afternoon, New Designer has changed.

I now have to click a tiny arrow button for each 'For Each', then each 'Condition', and then each 'IF No' to expand the actions and access the fields I need to change. Clicking each of these buttons, sometimes more than once because the mouse cursor has to be in just the right spot, causes the user interface to move around so it's not possible to do this very efficiently. It's a horrible UX but it doesn't stall on me.

Most importantly, New Designer doesn't always connect to the source so I need to either refresh the page and/or switch back to Good Designer. Evidently there's now some new "Publish" function which seems to be interfering with something.

So, I'm stuck. Because of some change that happened within the past two hours, I can not get Power Automate Designer to connect to anything. Previously, I could delete the Planner Group ID I want to replace and it would populate with all the groups I'm a member of. Now, after I delete that value, I get an error about Request to Azure Resource Manager failed with error: '{"Code":"NotFound", "Message":"Cannot find connection with name blah blah blah.

Please stop making everything worse. I am exhausted with five minute tasks having to take hours or days just because Microsoft feels like making needless changes. Another example it this horrible forum platform. Why change something that has worked without issue since the dawn of the internet?

Categories:

Building flows

I hear you with the frustrations with the new designer. When I was at the Power Platform Conference is was brought up there several times and the folks from Microsoft said they were working on making it 100% on parity with the old/classic designer. I don't think they are there yet.

One of the biggest things I hate about the new designer are actions that point to SharePoint lists and Document libraries. When you create the flow, you choose the list or library name. But when you go back to edit the flow, it shows the unique ID of the list instead:

This is a pain because then I don't have a visual confirmation as to what list on the SharePoint site the flow is connected to without switching to the old designer or opening an item in every list in the site until I find the list with the matching ID.

And if you open the flow and you are not the primary owner, it shows invalid connections like in my screen shot above, which always worries me. Switch to the old designer and this error goes away even if you open the flow checker.