Power Automate Ideas

michowl · ‎02-14-2017

I understand the current limitation on renaming an Action that has subsequent actions that depend upon it. I'd like functionality to be implemented that will refactor the flow (rename subsequent uses of the Action's output) when a rename occurs, so that I can rename an Action that has dependencies upon it. Kind of like how in Visual Studio, I can select a variable name, right click and select rename and it will rename all uses of the variable.

briangre · ‎07-10-2017

It is a common scenarion in on prem SharePoint to utilize Information Management Policies at the site collection scope to initiate workflows. Currently there is no way to trigger a workflow from a SharePoint Online retention policy.

michowl · ‎01-27-2017

The Compose action's field becomes read-only after it runs once. In complex flows that depend on long chains that are dependent on each other, I've had to delete and re-create up to 7 Compose Actions everytime I needed to make a small change in one of the ones at the top. This is far more common while using Compose Actions to create more and more complex flows.

ErichH · ‎06-26-2018

TODAY the first save of newly created FLOW triggers the flow to RUN. This is unwanted. it is just a save action (not save and test). This impacts especially Recurrence, Mobile button trigger and can lead to unwanted emails, recard actions etc. REQUEST: all new flows should be created with Status "disabled" similar to when a flow is copied. Details of TODAY's behavior and issues can be found here https://powerusers.microsoft.com/t5/I-Found-A-Bug/first-save-of-newly-created-FLOW-triggers-RUN-result-is-unwanted/m-p/129254/highlight/false#M2412

michowl · ‎09-22-2016

Would it be possible to remove, disable or hide fields and features that are not implemented? If non-implemented fields were grayed out and users could not interact with them, then users could see what future features are coming without productivity being lost on trying out features that do nothing. Currently, if I am trying something, I will lose a significant amount of time trying a feature and attempting to figure out if I "am doing it right" only to resort to asking a question on the forum and finding out it's not implemented.

bishnubhagat · ‎12-04-2017

At present in the VSTS Connector, there are only limited fields to map. Type, Title, Description, Priority, Area path, Iteration path etc. However, it would be very uselful, if we could map TAGs attribute as well in the connector along with the flexibilty to map extra fields those are quite important. At present we need to write custom code, if we need to map such field.

michowl · ‎02-03-2017

I have a few flows that work together in association for a given scenario. It would be great if there was some mechnism for pairing them in a template or associating them somehow. One example is: 1- New VSTS work items create new sharepoint items 2- Modified VSTS work items update sharepoint items 3- Modified Sharepoint List Item create or update VSTS work items (I found that creating a sharepoint list item triggered both "when a SP Item is created" AND "when a SP item is modified") Another is a flow that 1- routes tweets based on sentiment analysis. Some go into CRM, others go into a list. 2- Every morning that list is compiled into a digest email and sent.

Share your ideas and vote for future features

Rename actions with dependencies

Flow needs a trigger based on SharePoint Online Retention Policy (Information Management Policy)

Compose field should be editable after running

change flow behavior on first save of newly created FLOWs to INACTIVE to stop unintential RUNS

remove, disable or hide fields and features that are not implemented

Visual Studio Team Services Connector - Should have TAG attribute To Map

Associated or Grouped Flows

Helpful resources

Make it possible to duplicate actions in a Flow

Copy action - time saver

Sharepoint Create Folder

set item level security in SharePoint

Need Triggers for Dynamics 365 Operation