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

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

Status: Under Review

Thank you for your suggestion.

Status: Under Review

We are looking at this. Thank you!

Status: Under Review

Thank you for the suggestion.

Status: Under Review

The recommended way to do this is to use approval flows. These can receive input from users and then proceed based on the selected input. 

Status: Under Review

Thank you for the suggestion, this is a great idea.

Status: Under Review
Status: Under Review

Thank you for suggesting this idea, it is a good suggestion!

Status: Under Review

Thanks for the suggestion, this is a good idea.

Status: Under Review

Thank you for the suggestion. As is covered in the comments this is not a bug but an important feature to avoid data loss -- this allows you to temporarily disable a flow, make corrections, and then enable the flow, running it over all of the events that happened in the interim. Without this functionality all of those business critical events would be lost.

 

That being said, there may be scenarios where you want to explicitly discard your business data -- to support that case we'll look at adding an option to delete the trigger data so you can start again from scratch.

Status: Under Review

Thank you for this idea.

Status: Under Review
Status: Under Review

You could do this by re-sending the approval request with a note that comments are required, but this is clearly not ideal. We'll look at a better way to do this. Thank you.

Status: Under Review

Thanks for the input, we will evaluate this for a future release.

Status: Under Review
Status: Under Review

Thank you for the suggestion. Today, we already support running in user context when there is a user present. For example, if I select a file in SharePoint and start a workflow on that file, that workflow can run in either my context, or the context set up by the author of the flow (as decided by the author). This is possible because we have the user's AAD identity and token when the user is invoking the flow.

 

However, for automated flows that run in the background, we no longer have any securable identity from the end user who happens to cause that event. As a result, we have no way to run on behalf of that user. That being said, we understand that this is important scenario and one we will see if there's some other way to solve.

Status: Under Review

This would be a very useful fix, thank you for your feedback.

Labels