cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: New
Status: Started

We are now working on this feature and will have it available for you soon.

Status: Under Review

Thank you for your patience as we review this idea. We do understand the points made in all the comments, and the business justifications. I may reach out to some of you to discuss further, and look foward to exploring options with you!

 

Thank you again,

Audrie

Status: Need Info

Hello,

Triggering flows from emails sent to Office Groups is supported in the Product.

You can do this by specifying the Group alias in the 'To', 'CC', or 'To or CC' fields in the "When a new email arrives" trigger. This will ensure that flow triggers only when the group receives the email.

Note: The connection used with this trigger should have access to the group.

Details

 

Please leave comments if I have misunderstood the feature request.


Thanks,

Sunay

 

 

 

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: 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: 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: Completed

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

Status: Completed

Good news: you can now create planner tasks with the new connector. Read more here: https://flow.microsoft.com/blog/planner-community-and-licenses/ - if you have futher requests for planner please open new suggestions. Thanks!

Status: Completed

The Teams connector now supports triggers. You can read about these new triggers here: https://flow.microsoft.com/blog/support-tickets-teams-sharepoint/

Status: Under Review
Status: New
Status: Completed

You can now mention other people in Teams, read more about how to do that in our latest blog post: https://flow.microsoft.com/blog/adaptive-cards-for-microsoft-teams-microsoft-flow-us-government-now-...

Status: Completed

You can now do this with the new Create Approval (v2) action. Read more here: https://flow.microsoft.com/en-us/blog/2019-release-wave-2-plan-and-may-updates-for-microsoft-flow/

Status: Under Review
Status: Completed

Good news - this item is completed, you can read about it in this blog post : https://flow.microsoft.com/blog/share-with-sharepoint-office-365/ - there are now triggers for both When an Item is delete and When a file is deleted. Thanks!

Status: Started
Status: Completed

We now support multiple-valued Person and Choice fields, read more here: https://flow.microsoft.com/blog/button-types-more/

Status: Under Review

We are looking into this item now and we hope to use versioning as previous values will be retained by SharePoint for a finite period of time as it's configured to do so when you use versioning. For now, as a workaround, if you are familiar with the REST APIs, you could enable versioning in the list or the library and then use 'Send HTTP Request to SharePoint' to get the current and previous values of the fields that were changed. 

 

Thanks,

Chaks

Status: New
Labels
>