cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: New
Status: Under Review

Hi all,

 

We understand the pain points expressed here, and we are currently investigating options in building granular flow triggers for item updates and column changes in SharePoint.

 

We respectfully ask for your continued patience on this topic for the remainder of this calendar year. We are committed to a viable solution for our customers worldwide, and will continue to post updates here as we solidify our plans (which will most likely be early next year). Again, thank you for your patience, and your feedback on Microsoft Flow integrations with SharePoint.

 

Thanks,

Chakkaradeep (Chaks)

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: Under Review

Hey folks -

 

Thank you for the responses.

I am following up with my team to see if we can add a trigger that allows you to trigger a flow off of a mailbox (irrespective of whether a given user is following / not following that mailbox.)

 

Stay tuned. 

Status: New
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: Under Review
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

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

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: 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: 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: 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: New
Status: New
Status: Started
Status: Under Review
Status: Under Review

Today this can be accomplished by using multiple flows pointing at the same business logic via an HTTP trigger. So for example:

 

Flow 1 with Trigger 1 and HTTP action

Flow 2 with Trigger 2 and HTTP action

Flow 3 with Trigger 3 and HTTP action

Flow 4 with HTTP trigger and your actions

 

This requires n+1 flows (where n is the number of triggers) but enables you to accomplish the scenario. Thanks!

Labels