How to build a working hours tracker
After I wrote the story about my very first MicrosoftFlow I was curious if I could do another one. So I don’t wanted to create a new flow, but to improve the one I created before. What I want to achieve: A flow button, from which different freelancers can submit their working hours for different projects in a SharePoint list which accessed by HQ. Bonus: I want to have a minimum troubleshooting feature :-).
Step 1: I started with a list in SharePoint and 5 columns: Project Name, Hours spent, Today’s date,problem, and User.
Step 2: I chose the manual trigger flow button:

For the Project Name, I decided to add a drop-down list of options for the different projects and called them Project A, Project B, Project C. Hours Spent is just a text field, Problem is a yes/no field and User is just the Users name so we get a better overview who submitted which row.
This was just easy!
Step 3: I chose Create item in SharePoint, and connected to my SharePoint site and to the list I just created:

I The Fields are chosen from the Add Dynamic Content menu so that my inputs from the mobile button fills my SharePoint list. Magic :-)
Step 4: I want a mobile notification and further action depending on if a problem was submitted or not for two reasons: On the one hand I wanted to give my users a confirmation, that this button works and on the other hand I want to provide help if users need it.

Step 5: notification for NO problem:

To customize this a little bit, I used the User name and some other details for the mobile notification. I dont need links or link labels here.
Step 6: The notification for YES problem is a bit more extensive plus I want to send an email to my user:

Step 7: Back to my SharePoint list I want to format the problem column:

so I get a clear overview which Projects need my attention! I sorted from yes to no and I’m done!

Bam! So if you are interested: this is the whole flow:

You May Also Like
How Dev Proxy teaches you to make your apps more resilient
I added Microsoft Dev Proxy to my Mermaid → Dataverse converter expecting a quick resilience check—and ended up discovering everything that was quietly broken. From long-running rollbacks and Azure …
Building Azure functions that never store secrets — ever
Build Azure Functions that never store secrets by using Managed Identity. Request tokens from IMDS or the App Service identity endpoint and assign Microsoft Graph app roles at deploy time with …
Introducing Mermaid to Dataverse Converter
ERDs are great for explaining data models, but they’re usually trapped in dead slide decks. With Mermaid and the Mermaid to Dataverse Converter, your diagrams become source code: versioned, …