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

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

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. 

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

 

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 🙂

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.

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?

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

 

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! 

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.  

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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,219)