I've beeing using it to solve business automation requests from department managers. Some examples are:
- File migration from SP to OneDrive
- Ticket assiging in SharePoint
- Resolved ticket notifications in SharePoint
- Ticket / File archiving in SharePoint
I've also used it in conjuction with PowerApps to retrieve PDF files from SharePoint libraries using the HTTP request blocks. Perhaps one of the coolest things I've done with it though is a weekly ticket report I created for the executives at my company. This lists how many tickets are open, resolved, and closed in the past week.
A couple of ways that we're currently using Flow at work:
First, we are using it to process and output results from Microsoft Forms entries. In one, we're outputting the results of the form into a shared Excel doc. In another form, we're using the results to populate a Word template and then emailing the completed form to the user.
I'm also looking at ways to integrate Flow into our Dynamics work, since that's the team I head up. A couple of experiments include populating leads from our Contact Us form. Another idea is to use Flow to watch Twitter for possible client leads, people complaining about their ERP system and so forth.
I've blogged about several of these on my personal site. I'm really excited about the potential things I can do with Flow and getting it integrated into everything I can.
I have a few of those. The trigger for mine is just a "Recurrence" so it says every day (M-F) at 8 AM go look at this spread sheet or SPList (either will work) and see if there are any items listed that have a certain criteria missing or a certain status and if so send the Salesman listed or whatever column you have for the person an email reminding them to do this.
I do feel it would work BETTER if you had it in a SharePoint list but you could still do it in excel if you just really needed it there. Especially for something like this because with a SharePoint list you can have a people field that will show the name but also have available their email address. If you do it in excel you will either need a column for name and a column for email or have in the flow where it looks for the email address based on the name. I don't like the Excel options for this personally because if there is a typo or something then it won't pull through the correct data.
Be sure to think through if a single person may have multiple. If they will have multiple on the list do you want it sending out an email for each item (each row) or do you just want a count. You can do it either way but it will be slightly different so think that through first.
Go start a new thread for this and I'm sure you will tons of good input. Tag me if you don't and I will post more detail on there.
When I started with Flow, I handled the purchasing on one of our accounts. Back then, the process was to have to add a PO to each invoice and send to our AP department for processing, one invoice per email. So I decided to cut some corners and for each invoice I added a PO to, I saved in a folder and it was automatically sent to the department for processing. Eventually we used Flow on the account for time off, purchase order, vendor setup, onboarding and termination. Now we are using it at the corporate level for multi level approvals by threshold amounts for work orders.
I use and develop flows daily!
Improving communication, e.g. delivering orders between departments
Making use of Planner
Planner is a great and intuitive tool, but few people have the time to even look at it (possibly because they spend a lot of time organizing their tasks with sticky-notes). I use Flow to create and assigns a task when certain conditions in a sharepoint group(Document library, document or List) are met. The assigned users then get notifications from planner instead of an email for them to write down on a sticky note.
Enforcing consistent file-structure / templates
Use Flow to creates and maintain file-structure, copies templates and resources with conistent naming conventions in sharepoint or common areas.
App / PowerApps Development
Flows usually triggers upon modifications in SP-lists and Excel documents, then updates list items and rows in excel tables. Its a bit tricky, and it requires a lot of careful coalesce usage to avoid data being overwritten where input is allowed in both PowerApp and Excel.
We have a large amount of excel sheets that functions both as user data input and output / analysis, some of the sheets have been developed for maybe 2 decades, if not longer. It's not easy for people that have been working with excel for so long to transition into something completely different, so I have to create a middle-ground. I believe that it not possible to improve something that is not fully understood, and I often imagine every person who works in excel have their own mental application where the sheet is the database; there is no way for me to understand it all at once. Finding a common ground for all users and their tasks is a challenge, but in my opinion the best way to improve something. Flow allows me to introduce and adjust alternative methods in parallel, that way it is their choice if they want to use the new methods I create instead. And as a bonus, this works as a kind of quality assurance for the new methods.
I built a workspace that is to be used as a document repository for Work Instructions for the operational teams in the organisation I am in. I learned using Flows by trial-and-error and built an approval flow that will notify a team manager in one of the processes, with an email, that a Work Instruction has been sent for review. Then the manager can approve/reject it and leave a comment if required.
Fingers crossed that there will be an option to make an annual review reminder, at some point.
Well my challenge is that, I would like to have this work based on the last modified date of an item. Ideally to add 6 or 12 months on top of that date, and then send a reminder. This would keep it more dynamic, but it is currently beyond my abilities.
I have set up a recurring flow to read the SQL Server Database Log File. When the Flow finds an error record logged it sends the System Administrator a High Priority email warning that shows what error occurred.
I am very hesitant to put any trust in Flow. it fails, it is hard to debug, it is unreliable.
I need this to run once a month when I get the email because after that, it is gone forever.
If I get Lucky, Flow will work but this is a gamble. I need to find something more dependable.
If it was just for a trivial thing OK but for mssion critical things I guess thie si not the right tool.
Gto me Flow is a cool toy, not a production ready tool.
There a re many instances of issues, here is an example.
I'm just a newby, just created my first 3 flows...
- an enquete (in Forms), I get the e-mail adressen from Excel, keep track for who responded en send an reminder after 2 weeks. The results are stored in an Excel-file. If I find the time I want to use this file in PowerBI to make management rapports and push them to other people (using PowerApps??)
-2 flows with information mails to 2 different groups, also using Excel, Forms.
Strange that you see such issues. I have been using Flow for numerous production uses for months now and have yet to see a single failure I could attribute to the Flow infrastructure. I do agree, however, that when a flow does fail, it can sometimes be somewhat difficult to debug the problem. But 99% of the time, when I struggle to find the reason for a failure, it's because the remote system that Flow connects to didn't provide any error details beyond a generic failure message. But that's hardly something I would blame on Flow, but rather on the remote API providers.
Best of luck to you!
Where would you want me to start.
We have a number of Flows working within our Education Tennat from creating Contracts from Word Templates, extracting Data from Excel and publising to CDS then refreshing Power BI as well as generating dynamic piping variables for MS Forms Pro Surveys that are tied back to Competence Managment Records in Dynamics 365.
I use Flow as a connective tissue to collate information across heterogeneous systems.
Fetch sale data from Salesforce
Save a shadow copy on Azure SQL / Cosmos DB
Cosmos DB / Azure SQL DB as the main databases for custom low-code automation using PowerApps interfaces
Prefilling SharePoint documents/columns with data from SQL
Complex automation as a part of a larger solution to auto-reply to client emails on a ticketing system which automatically creates DB ticket rows and saves attachments to disk on a folder specific to the client and ticket ID.
Track sent emails that match same tickets to complete information control on client requests.
Hi everyone. I work within my company's IT infrastructure organization. I currently use Flow for two main purposes:
1. We receive service requests from many different individuals across the company for things like server builds, capacity increases, server decoms, etc. I built a service request form in Forms, access those variables in Flow, and then create / tag / link all of the tasks associated with each specific type of request in a project in Azure Devops. (plus sending out email notifications about the new request)
2. We've previously written some extensive on-prem automations in System Center Orchestrator for building/configuring servers, scheduling snapshots, and decommissioning servers. I'm now using the same combination of Forms/Flow mentioned above to give end-users the ability to trigger some of those functions themselves. Flow takes the inputs of the request and feeds them through to the gateway we've installed on our Orchestrator server where it can be picked up and run by Orchestrator. It has proven to be a great hybrid solution.
Completed my first Flow (Power Automate) and must say, its easier than I thought conceptually. I do agree with other posts than when something breaks, its tricky to troubleshoot. I had to use the "test" function to see where the issue was.
I used flow to automate a serial approval workflow for any new requests for R&D. The request originates in an app I built in Power Apps, which feeds into a Sharepoint list that I also created. By default the status is pending. Once the request is submitted an automatic email to Accept or Reject is sent via Outlook. Depending on the outcome, Flow determines whether to proceed with getting the second approval. At all decision juncture, SharePoint list is updated with the latest decisions. Seems to work well. One annoyance is that once a decision is made in Outlook, it launches a website that confirms that the decision is "registered". Anyway to get rid of this? Feels like a pop up ad.
i use flow to make up for the limitations in Powerapps referencing profile fields.
The Azure AD profiles should allow the use of mapped custom fields and allow them to be refernced in Powerapps to fill in user data automatically.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.