Power Automate example to create unique Emails from groups of data in Excel to email Employees their unique items

[MichaelGernaey]

By submitting this pull request, you agree to the contribution guidelines

If you aren't familiar with how to contribute to open-source repositories using GitHub, or if you find the instructions on this page confusing, sign up for one of our Sharing is Caring events. It's completely free, and we'll guide you through the process.

To submit a pull request with multiple authors, make sure that at least one commit is a co-authored commit by adding a Co-authored-by: trailer to the commit's message. E.g.: Co-authored-by: name <[email protected]>

Put an x in all the items that apply ([x], without spaces), make notes next to any that haven't been addressed.

• Bug fix?
• [X ] New sample?
• Related issues: fixes #X, partially #Y, mentioned in #Z
• [X ] Needs API permissions? (SharePoint, Excel Online Business and Outlook 365 connectors)
• [X ] Has other prerequisites? (Documented in the README.md, SharePoint, Outlook, Excel Business aka M/O365 account)

What's in this Pull Request?

The is a brand-new sample, that leverages Excel, SharePoint and Outlook 365. It illustrates how to send an excel file that has a list of workitems in an excel table with headers. The flow will trigger, validate the incoming excel attachment and then process the file by first saving it to a SharePoint document library, then list all the rows in Excel. It will then use a unique list of email addresses, composed from the excel data, to group all workitems by unique email address and then email the employee their workitems in an HTML Table

A Flow Example
An Excel file called workitems.xlsx which is used by the flow
A word document in the assests which provides direct details of every action, it is essentially a business process functional and technical specification document
images for the README.md
instructions on what to do

Checklist

This checklist is mostly useful as a reminder of small things that can easily be forgotten – it is meant as a helpful tool rather than hoops to jump through.

Put an x in all the items that apply ([x], no spaces), make notes next to any that haven't been addressed.

• [X ] My pull request affects only ONE sample.
• [X ] I have updated the README file.
• [X ] My README has at least one static high-resolution screenshot (i.e. not a GIF)
• [X ] My README contains complete setup instructions, including pre-requisites and permissions required