Currently, it is supported only for events created in the user mailbox in case of using "Event Create" of Office 365 Outlook as a trigger in Flow. In order to improve convenience, I would like you to add a feature that allows activating the trigger for event creation regardless of mailboxes, such as Room Mailbox and Equipment mailbox or else.
In addition to this, it will be greatly helpful to let the users know about the details or note of the meetings if you can send the notifications based on the schedule of the Meeting room individually.
I have this in mind particularly for teams which include external users, such as on a construction project. The external folks might fill out a Forms form requesting access to the Team, or perhaps there would be a spreadsheet sent from a partner org, listing people who should have access. Then the Flow would add members to the project Team without an admin needing to do that for each person - maybe the admin would just approve them as they come in.
Add a feature that will allow flow to disable event firing when updating a SharePoint list item, so that the Flow doesn't get stuck in a loop. Currently if I create a flow with a SharePoint list trigger when item is created or modified and have the Flow update a field in the item the loop gets stuck in a loop. One workaround is to add logic to check if the field(s) still need to be updated and if not then don't update the item but even in that case the flow will be triggered twice. It just makes sense to have an option that will allow Flow to update an item without triggering an event that will cause the same Flow or another Flow to run against the item again.
I have created a couple of flows under my own account, but I want to change it to a generic user in order to make sure that the flows keep running should my account be deleted one day.
I can add an owner to a flow, but behind the scenes I continue to be the original owner it seems. One example is that sending mails in a flow is done showing my name. The same goes for approval mails as part of the 'Start an approval' action.
It would be useful to have some kind of functionality to easily change the original owner of a flow.
How about adding the ability to trigger based on date and time?
The basic scenario would be manually entered date/time or recurring date/time, such as “every Monday morning do this...”
It would be really useful though, if triggers could be based on data in various apps and services. Here are some examples:
1. A property on a SharePoint/OneDrive document library or list. It could be “100 days after file created” or “when this date/time in a custom column occurs”. We have a use case, where contracts are stored in a doclib with custom columns for expiration. It would be very useful to be able to trigger a workflow on or before those dates occur.
2. Outlook reminders, on/before/after meetings occur or on/before/after tasks are due
3. Planner, ToDo and classroom assignments are all services that have due dates, which could benefit from reminders before or on the date, but also after to follow up or be reminded of overdue tasks.
Those were just some examples, but basically anywhere dates and times are to be found, either as existing fields or custom, would be applicable.
It would be helpful if we could search throguh the run history. Imagine being able to search for a file name and search looks at every bit of output from any action or trigger to find the related flows.
I have many flows and they get initiated many times during the day. When I am managing the flows and try to solve some issues it is very hard to find the flow instance I am looking for because the display is in Time Ago instead of a datetime. It makes it a lot more confusing especially when trying to solve problems with flows in the past as all of them will just show generic "One week ago" and you can not tell which date it was. I often know the exact time I need to find but because the display is in Time Ago I need to go into every single one until I find the required on.
Solution: I think the best solution would be to have an option for date display, Show actual datetime or Show Time Ago which we could switch between.
THis would be huge Quality of Life improvement for me and I think other developers as well.
As a user of Flow I should be able to create a Workitem Query Action (on the VSTS Connector) that utilizes dynamic values.This would allow me to look up Work items based on the results of previous Actions in my Flow.
For example, if a previous Action outputted a string, I should be able to look up work items that contain those words in their title by specifying:
I'd like to be able to trigger a flow from MS Teams if I am "@" mentioned or if a group to which I belong is "@" mentioned. It would be really useful to be able to set up secondary notifications whenever someone is trying to reach out to me or my team.
In my humble opinion, the various task tools are seriously lacking. You can create and manage To-Do's/Tasks in 4 different areas of 365.
1.) Project Site Task List
None of these seem to speak with eachother and I am sure that I speak for many when I say that having to go to four different apps to manage my tasks is rather tedious. We need a way to integrate or push updates between the apps for Tasks. While I understand OneNote wouldn't really connect to the rest for various reasons, I think there still should be some sort of the solution for the rest.
In my perfect world, the new To-Do's app would be the hub for any task assigned to you (whether in Planner or a Project Task List) as well as a location to create separate To-Do's for yourself.
As is, I and our users find the lack of integration between all of the different task managers tedious and many tasks get lost in the shuffle.
Paige Elmore IT Project Manager Charlottesville, VA
In Approvals, there must be an option to change the From address. I have almost 7 Flows in creation and all are stuck in this thing. I wanted to have a Created By email in the From address rather than the one who created the Flow.
Currently we have Nintex, SharePoint Designer, and Flow workflows. We are trying to give the direction that all new flows should be created using Flow if possible so we only have to support one tool over time. We are a hybrid organization and it will be years before we are completely in O365. Without this working, we can't leverage this approach.
Working with flows is very messy if you are working on a batch of flows that contribute to one task. A system of being able to tag flows or put them in folders would allow you to work more seamlessly on specific flow groups.