cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: Under Review

Our recommendation is to use Solutions to organize your flows. We are also looking at if there are additional organizational capabilities that we can add to help you organize your flows.

Status: New
Status: Completed

Hi all,

 

Happy to update that this feature is now rolled out to and available for use. The documentation is updated as well:

For more info about how to use this action, see this tutorial: Introducing 'when an item or file modified' trigger and 'Get changes' action

 

Thank you all for the feedback and please let us know if you have any questions.

 

Thanks,

Chakkaradeep

Status: Under Review
Status: Completed

You can work with checklists in the Planner connector - read more here: https://docs.microsoft.com/en-us/connectors/planner/#update-task-details

Status: Completed

This day has finally arrived when Flow supports copy paste.

Although it seems like a simple feature to build, there is a lot of complexity involved in supporting this feature. Especially when you think about handling references and action names across flows.

 

I appreciate all the feedback on this post, and know that you've played a very important role in shaping the future of Microsoft Flow.

 

More details on Clipboard support here: https://preview.flow.microsoft.com/en-us/blog/introducing-clipboard-in-flow-designer-and-three-new-u...

 

Highly recommend reading through, if you are a fan of easter eggs 🙂

Status: Completed
Status: Under Review

This is a great suggestion - we are trying to identify a way to safely run regex in Flow.

Status: Under Review

We will look at enhancing this connector - but this connector is open source which means that anyone can contribute to it and add the capabilities. See more here: https://github.com/microsoft/PowerPlatformConnectors/tree/dev/certified-connectors/Planner

Status: Declined

This can be accomplished by using multiple flows pointing at the same business logic via a child flows:

Flow 1 with Trigger 1 and Child flow action

Flow 2 with Trigger 2 and Child flow action

Flow 3 with Trigger 3 and Child flow action

Flow 4 with Button trigger and your actions

 

We do not have any plans to have many triggers in a single flow.

Status: Completed

You can now organize your flows into solutions. Solutions are like tags or folders. They are like folders in that they can contain flows, plus they can contain other assets like PowerApps, CDS entities etc.... They are also like tags in that a single flow can be in more than one solution - so your not tied to one strict heirarchy. The new Solutions tab is available for any envirnomnet that has CDS enabled. Read more here: https://flow.microsoft.com/blog/solutions-in-microsoft-flow/

Status: New
Status: Declined

Hi all,

 

After thoroughly reviewing this idea, we have decided not to proceed with this idea for a couple of reasons.

  • SharePoint events are no longer event receiver based and are performed using webhooks or polling where applicable
  • Other Office 365 applications and internal systems like auditing may and will rely on such changes like updates to items, files and other entities in SharePoint

However, that said, we understand the crux of the issue which is to help avoid loops. We will work with the flow team to come up with a generic model/pattern that applies across data source/connections for similar scenarios.

 

Thanks all for your input and please submit/vote your ideas as we are actively monitoring the ideas forum.

 

Thanks,

Chaks

Status: New
Status: New
Status: Started

Hi all,

 

Happy to announce that we started the development of building granular trigger for SharePoint item and file changes along with the plan to provide old and new values.

 

To be able to infer and provide old and new values, we will first need the ability for a trigger that can run when an item is modified and then the ability to get what changed for that modified item. So, to support this, we will be releasing a new trigger and a new action that works along with this new trigger to help you get started. 

 

  1. 'When an item or file is modified' trigger
    1. Only triggers on an item or file updates, not on an item or file creation.
  2. 'Get item or file properties changes' action
    1. This new action returns information about whether or not a column's value was modified.
    2. This action when released will:
      1. Only work with the 'When an item or file is modified' trigger.
      2. Require versioning to be turned on for the associated list or library 

 

With these two updates, you can now build a flow when someone modifies a list or library and then using the new action check if a particular column or file property was modified since the last flow run. For example, you can check if the Status column was modified since the last run and then get the current Status value, else do something else.  

 

After this update, we will continue to work on enabling the 'Get item or file properties changes' to provide old and new values of the columns. 

 

Thank you all for being patient with us. Will update this thread as we have more updates.

 

Thanks,

Chakkaradeep

Status: Completed

Hi all,

 

The following two actions should now be available:

1. Grant access to an item or a folder

2. Stop sharing an item or folder

 

Please check out these new actions in the SharePoint connector and let us know if you have any feedback! 

 

 

 

Thanks,

Chaks

Status: Completed

This item was part of the October 2019 release : https://flow.microsoft.com/blog/october-updates-for-microsoft-flow/

Status: New
Status: Completed

You can now customize who the Approval appears from - read more here: https://flow.microsoft.com/blog/button-types-more/

Labels