cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AnnaChu
Employee
Employee

Help make Flow Design easier

The Power Automate Designer team would love to hear feedback from the perspective of novice Power Automate users, citizen developers and low coders on their experience with Power Automate Designer. When designing flows, what do they struggle most with? If this sounds like something you’ve heard someone mention, please forward them this pre-screening survey to complete: https://aka.ms/MPA_DesignerFeedback

 

@kishbuy238 and team are interested in hosting a screen-sharing session to identify opportunities to improve the experience. This survey will be open through to August.

134 REPLIES 134
ryleybauer
Resolver II
Resolver II

Access to Version history on flows for when I mess up my flow and forget how to fix it! (I know there is solution level versioning, but that's not granular enough)

 

A container class (like Scope) that supports initializing variables, so I can collapse all my declarations at the beginning of my flow to "move them out of the way" so we can see the useful actions at a glance. Maybe this could even be accomplished by an "Initialize VariableS" action where we can stack them in a collapsed UI similar to conditions on a Condition control. Maybe even grouping by type in the same way that conditions can be grouped/nested inside of AND/OR branches. 

 

A better way/more native way to call PowerShell than setting up runbooks as the increased permissions required to enable and configure them in Azure leaves it as an inaccessible method to citizen developers. If the user has permission to run the script, but no access to Azure then they can't make a flow to call that script programmatically. 

 

I noticed when you copy/paste actions, that a GUID is stored in the clipboard. The ability to share Steps/Actions would be huge. I think about using OneDrive and sharing a file vs a folder when I think about sharing a step vs a whole flow. It'd be hugely collaborative to share a link to a single action with a peer, whether for collaboration or just to share as a template. I recognize this is a huge ask as the current permissions aren't structured this way. 

ryleybauer
Resolver II
Resolver II

A weird quirk that complicates my development is when I go to select dynamic content from an action which contains multiple copies of the same key at different levels of a JSON payload. 

i.e. 

{"result":[

   "key": "value"

   "result": "value"

]}

How do I identify which "result" I'm selecting? The only way I can usually do it is to ADD the dynamic content, then hold my mouse over it for the tooltip that reveals the whole object path. Can we add those tooltips to the dynamic content window so that I know which layer I'm in BEFORE I add it? 

ryleybauer_0-1656609511508.png

 

ryleybauer
Resolver II
Resolver II

This one will probably be contentious:

 

The ability to still save a flow even if it's in an error state. I can't tell you how many times I've had to stay at my desk for an extra hour or two trying to get it to a working state so I can leave it and come back without worrying my progress will be wiped out by my browser timing out.

Warn me, wave a flag to suggest I don't do the dumb, leave a banner on screen to remind me I really shouldn't have, automatically disable my flow and harass me with email reminders to fix it, but straight up blocking me from saving my progress while troubleshooting is a major inconvenience. 

Acknowledged the request. Thank you 🙂

eliotcole
Super User
Super User

Have a bit more of an 'equality' to the interface.

 

For example, only a few people know about trigger conditions, but even less will use them because it's just a text field.

 

Yet for those that know, you can pretty much construct a trigger condition using the Filter action's interface, then paste from the 'advanced' view of that.

 

Of course it's not as good as using the actual Condition action's interface, which would really allow one to build a properly good, deep, set of AND/OR conditions into a trigger condition. That said, I am aware that using multiple conditions is akin to one big AND set. Still, not everyone is, and it's still slightly painful for some to work out even placing a few expressions with commas in some brackets and an @ or before them.

 

I'm using Trigger Conditions as an example, here, but they're not the only offender here. Oh, and I'm not saying this as a soapbox thing ... I love Power Automate, nothing else touches it. I just think that applying some of the flourishes that exist for one thing, to those elsewhere would hugely benefit the interface.

 

Perhaps another example (I'm in the beta view) would be not having the more 'full' expression builder in the map field of a Select, but having it for the From ... and being pushed back into the old view. Equally ... I don't think a *lot* of users will like the "more 'full' expression builder" because they can't just tap on a function to pop it into the builder. I think there's got to be a way to have access to the Dynamic Values AND the tap to include functions below that builder ... maybe some tabs? I dunno.

Or at least be able to save it in draft mode, so if you are making edits to a workflow that is being used, the current published workflow continues to work until you publish the one in draft. Nintex has this feature for their workflow designer, so I don't see why Microsoft cannot do this with Power Automate.

KarlH
Advocate I
Advocate I

So glad you've posted this. I've filled out the form, hope to hear from your team for a catch-up. 

I may have missed something, but doesn't this also depend on well managed 'required' fields?

iso
Advocate IV
Advocate IV

1_Implement proper scoping, as in C/C++, C#, Java, etc...

2_Have an option to force a connection to refresh so that users won't have to delete/recreate a connection just so that it picks up whatever changes were made to a Form, DB table, etc...

3_Allow variable self-reference in a SET VARIABLE action, ie x = x+1, for any data type.

4_Enlarge the Dynamic content/Expression dialog that pops up after clicking in an input text field, and when clicking in Expression, pop-up a bona fide code editor that can be resized to the whole screen if need be. As it stands today, I gotta shuttle back and forth between the designer and my fav editor.

5_Fix the Javascript slowdown of the UI after leaving the designer open for more than 5 days in Chrome.

iso
Advocate IV
Advocate IV

1_Implement proper scoping, as in C/C++, C#, Java, etc...

2_Have an option to force a connection to refresh so that users won't have to delete/recreate a connection just so that it picks up whatever changes were made to a Form, DB table, etc...

3_Allow variable self-reference in a SET VARIABLE action, ie x = x+1, for any data type.

4_Enlarge the Dynamic content/Expression dialog that pops up after clicking in an input text field, and when clicking in Expression, pop-up a bona fide code editor that can be resized to the whole screen if need be. As it stands today, I gotta shuttle back and forth between the designer and my fav editor.

5_Fix the Javascript slowdown of the UI after leaving the designer open for more than 5 days in Chrome.

eliotcole
Super User
Super User

Hi, @AnnaChu, I've thought of something that will really help make Flow Design easier:

 

Do Not Remove The Graph API Functionality From The Office 365 Groups Connector Action "Send an HTTP request"

 

You would basically be destroying HUGE swathes of usability of the system, forcing users into needlessly complex routines using Azure apps, which just need a simple HTTP call.

 

I've created an "Idea" to bring this to the fore, here:

https://ideas.powerautomate.com/d365community/idea/d51463df-6f0c-ed11-a81b-6045bd7c3e3f

 

If they're aware of this action's power, I'd call on my fellow Flow Ninjas, @Pstork1, @Expiscornovus, @tom_riha, @ScottShearer, @annajhaveri, @takolota, @ekarim2020, @Paulie78, @MarconettiMarco, @fchopo to join me in protesting the removal of such a tool.

 

(sorry for @'ing you all, folks)

 

If they aren't aware of it's usability, then I suggest they perform just any simple (non-groups 😉) Graph call in V1, and then try it in V2.

 

Here's some pictoral evidence of the change:

Send an HTTP request
wah1.jpg
Send an HTTP request V2
wah2.jpg
Current docs page (no V2 listed)
Spoiler
wah3.jpg

 

That Idea again:

https://ideas.powerautomate.com/d365community/idea/d51463df-6f0c-ed11-a81b-6045bd7c3e3f

 

Do not do this to us, Anna, what's the point of an automation service that can't automate?

NeonThunder
Advocate I
Advocate I

Please let us organise our flows into folder and tag them.  At the moment it's a nightmare seeing which flow does what in a big list

BrianS
Super User
Super User

Knowing what the Flow needs in a given field - is it the ID, the Identifier, etc. It would help if the naming convention was a little better

Sourceress
Frequent Visitor

Understanding the difference between 'Equal To' and 'Contains', particularly when leveraging dynamic variables. There was a brilliant resolved post on this issue I can no longer access, which drives me wild.

https://powerusers.microsoft.com/t5/Power-Automate-Ideas/Improve-Is-Equal-To-and-Contains-Condition-Functionality/idc-p/1642981#M29485

 

eliotcole
Super User
Super User

Hi, @AnnaChu, something that I noticed the other day is that the forum has removed the "I've found a bug" section, plus there's nowhere to adequately ask for help with/for/about the forum itself. These feel like more things (in addition to the Graph API action) being taken away that reduce our ability to easily design flows, because they affect the very ability to report problems with that, and/or the only real interaction the community has on building flows.

 

Could we be appraised of what we should use in place of these functions? As it appears that this is the only thread relevant to either. 😅

Redders
Continued Contributor
Continued Contributor

Hi @AnnaChu,

 

I have complete the form on the initial post. I thought that I would add my comments in here too.

 

@ryleybauer mentioned about the ability to save in an error state, which I love and the ability to have a version history, my idea to make the UI easier to use is along similar lines.

 

Often I find myself half building flows just so that I can get data from the first part (HTTP requests being top of my list) just to re-edit the 2nd part of the flow (Parse JSON). It would be really useful to be able to make steps inactive or greyed out so that the flow could be build/saved without the required information being added. 

 

It would also help when encountering issues with a flow when attempting "something different" that doesn't quite work as well as the initial design. This means that you have to delete and re-build when you could just make steps active and inactive accordingly.

 

Would this resolve some of your issues too @ryleybauer?

That would be awesome! 

stayinginsync
Advocate II
Advocate II

I have found that several of the Template submitted to the Flow Community, or published directly by Microsoft, are not available in the GCC environments.  I end up having to go into my Developer account to find a template and then recreate them manually, which takes additional time.  Two in particular I can point to are the Templates for Forms and OneNote.  Neither of which are available.  

stayinginsync
Advocate II
Advocate II

Did you know that it was this hard to work with OneNote Notebooks in Flow (especially Shared Notebooks in Teams) - Power Automate solution: OneNote action errors involving invalid or inaccessible Notebook Keys and s... I would never have gotten my flow to work without this resource, and even then, I still cannot set or update the page title.

 

I had to create a delay, such as discussed here (Solved: Re: Get updated OneNote title and link - Power Platform Community (microsoft.com)) because the flow was sending instantaneously after a page was created without capturing the page title.


@ryleybauer wrote:

Access to Version history on flows for when I mess up my flow and forget how to fix it! (I know there is solution level versioning, but that's not granular enough)


^^^ THIS.  Not just for development improvement, but also for organizational retention or if the Flow is built in Teams, not a solution. 

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (3,428)