Hi All,
Need your help to build a flow using below sample data from SharePoint List that should deliver an HTML Table to specific App Owner and Escalation Focal. I have built a flow but not sure how to capture each manager from App Owner since this is multiselection Person field on SharePoint.
I would appreciate if you can guide me from where to start and construct
Application ID | Application Name | Domain | Application Type | PlannedUpgradeDate | Actual UpgradeDate | GI Status | KPI Days Left | AppOwner | Escalation Focal |
112233 | MOTS | Diamond | Prod | 5/7/2023 | 3/20/2023 | Upto Date | 25 | Sanjay Singhania | Ram Narayan |
112233 | MOTS | Diamond | Non-Prod | 4/27/2023 | 3/30/2023 | Upto Date | 15 | Sanjay Singhania | Ram Narayan |
223344 | Treas_Opex | Nickel | Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Chris Almon |
223344 | Treas_Opex | Nickel | Non-Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Chris Almon |
356578 | Titanium_tel | Titanium | Prod | 4/12/2023 | 4/14/2023 | GI Overdue | 0 | Satish Rai; Timothy Bulock | Ram Narayan |
356578 | Titanium_tel | Titanium | Non-Prod | 4/5/2023 | 4/21/2023 | GI Overdue | -7 | Satish Rai; Timothy Bulock | Ram Narayan |
465789 | CropsEpX | Jewel | Prod | 4/17/2023 | 4/9/2023 | GI Due | 5 | Sanjay Singhania | Chris Almon |
465789 | CropsEpX | Jewel | Non-Prod | 4/17/2023 | 4/9/2023 | GI Due | 5 | Sanjay Singhania | Chris Almon |
245356 | MOTS_topical | Titanium | Prod | 5/9/2023 | 3/18/2023 | Upto Date | 27 | Satish Rai; Timothy Bulock | Suraj Devathali |
245356 | MOTS_topical | Titanium | Non-Prod | 7/11/2023 | 1/14/2023 | Upto Date | 90 | Satish Rai; Timothy Bulock | Suraj Devathali |
223344 | Treas_Opex | Nickel | Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Chris Almon |
223344 | Treas_Opex | Nickel | Non-Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Chris Almon |
Solved! Go to Solution.
Hopefully this is what you're looking for.
For this example, I'm using the following SharePoint List. App Owner is a Person field set to multiple select. Application Name is using the Title field (just renamed it).
See full flow below. I'll go into each of the actions.
Get items retrieves our list items.
XML is a Compose action that converts our data to XML so we can use XPath expressions to extract the App Owners. The expression used is:
xml(json(concat('{"root": { value:', outputs('Get_items')?['body/value'], '}}')))
Select extracts out all the App Owners across the list items. This will allow us to iterate over each one to get their items and send an email. The expressions used are:
//From
xpath(outputs('XML'), '//root/value/AppOwner')
//Map
json(item())?['AppOwner']
Style HTML table is a Compose action that contains some CSS for styling the HTML table so it looks nicer in the email sent out.
<style>
table {
border-collapse: collapse;
}
table td,
table th {
border: 1px solid #ddd;
padding: 6px 20px;
text-align: left;
}
table th {
background-color: #1C6EA4;
color: white;
}
</style>
Apply to each iterates over each of the App owners. It uses the following expression to remove duplicate values so we only iterate over each App owner once.
union(body('Select'), body('Select'))
Filter array uses the output from Get items and checks to see if App Owner contains the current App Owner we are iterating over.
Create HTML table uses the output from Filter array (the items for the current App Owner) and maps out the fields we want to show. Below are the expressions used for each of the mappings.
//Application ID
item()?['ApplicationID']
//Application Name (uses the Title field in our SharePoint list)
item()?['Title']
//Domain (Need to get the value sinces it's a Choice field)
item()?['Domain/Value']
//App Owner(s)
join(
union(
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()')),
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()'))
),
', '
)
//Escalation Focal
item()?['EscalationFocal/DisplayName']
//Other fields
item()?['NAME_OF_YOUR_FIELD']
Escalation Focal Emails is a Compose action that retrieves each of the Escalation Focal emails that are related to the records in the current HTML table data. It removes duplication emails and joins them with a semicolon so we can use them in the CC field in our email.
join(
union(
xpath(outputs('XML'), concat('//root/value[AppOwner/DisplayName="', item()?['DisplayName'], '"]/EscalationFocal/Email/text()')),
xpath(outputs('XML'), concat('//root/value[AppOwner/DisplayName="', item()?['DisplayName'], '"]/EscalationFocal/Email/text()'))
),
';'
)
Send an email (V2) uses the output from Style HTML table and Create HTML table in the Body, and the output from Escalation Focal Emails in the CC field. It also uses the following expressions for the To field and the Display Name in the body.
//To
items('Apply_to_each')?['Email']
//Display Name (in the Body greeting)
items('Apply_to_each')?['DisplayName']
A couple of sample emails sent out are below.
Below is the expression for getting the App owners. You may need to change the field name to suit what you have.
//App Owner(s)
join(
union(
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()')),
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()'))
),
', '
)
What is the error message you are getting?
Try the expression below:
first(split(item()?['Days_Left'], '.'))
Just to confirm what you're after. Given the App Owners and Escalation Focal users in your list above, would you expect to send out 4 emails (one for each App Owner) and 3 emails (one for each Escalation Focal user) = total of 7 individual emails sent out, with only records that are related to each particular user?
I want to send an HTML Table clubbed all records of those App Owner in (TO:) and Escalation focals in CC.
All their records should be clubbed in an HTML Table. They should not receive any different records which do not belong to them.
more of like a personalized mail. just help me to get Person Name for each record since it is multiselection person field and put it in the HTML Table. (if case of two app owners they should appear together in the column)
for example: see below email.
Sounds good - I can work on it when I wake up (1.30AM for me at the moment so off to sleep).
Just a bit unsure about the CC for Escalation Focals. If I send an email to Timothy Bulock with just their records, who would I CC as there are multiple Escalation Focals across his records?
Hi @grantjenkins ,
Of course Rest well 🙂
Please note. Whichever record has multiple App Owners they all should get email as TO:
also they both should appear in the HTML Table against their records next to each other separated by a comma or semicolon.
Hi @grantjenkins,
edited table data correctly.
Application ID | Application Name | Domain | Application Type | PlannedUpgradeDate | Actual UpgradeDate | GI Status | KPI Days Left | AppOwner | Escalation Focal |
112233 | MOTS | Diamond | Prod | 5/7/2023 | 3/20/2023 | Upto Date | 25 | Sanjay Singhania | Ram Narayan |
112233 | MOTS | Diamond | Non-Prod | 4/27/2023 | 3/30/2023 | Upto Date | 15 | Sanjay Singhania | Ram Narayan |
223344 | Treas_Opex | Nickel | Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Suraj Devasthali |
223344 | Treas_Opex | Nickel | Non-Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Suraj Devasthali |
356578 | Titanium_tel | Titanium | Prod | 4/12/2023 | 4/14/2023 | GI Overdue | 0 | Satish Rai; Timothy Bulock | Ram Narayan |
356578 | Titanium_tel | Titanium | Non-Prod | 4/5/2023 | 4/21/2023 | GI Overdue | -7 | Satish Rai; Timothy Bulock | Ram Narayan |
465789 | CropsEpX | Jewel | Prod | 4/17/2023 | 4/9/2023 | GI Due | 5 | Sanjay Singhania | Ram Narayan |
465789 | CropsEpX | Jewel | Non-Prod | 4/17/2023 | 4/9/2023 | GI Due | 5 | Sanjay Singhania | Ram Narayan |
245356 | MOTS_topical | Titanium | Prod | 5/9/2023 | 3/18/2023 | Upto Date | 27 | Satish Rai; Timothy Bulock | Ram Narayan |
245356 | MOTS_topical | Titanium | Non-Prod | 7/11/2023 | 1/14/2023 | Upto Date | 90 | Satish Rai; Timothy Bulock | Ram Narayan |
223344 | Treas_Opex | Nickel | Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Suraj Devasthali |
223344 | Treas_Opex | Nickel | Non-Prod | 4/22/2023 | 4/4/2023 | GI Due | 10 | Vijay Pawar; Teddy Santos | Suraj Devasthali |
Hopefully this is what you're looking for.
For this example, I'm using the following SharePoint List. App Owner is a Person field set to multiple select. Application Name is using the Title field (just renamed it).
See full flow below. I'll go into each of the actions.
Get items retrieves our list items.
XML is a Compose action that converts our data to XML so we can use XPath expressions to extract the App Owners. The expression used is:
xml(json(concat('{"root": { value:', outputs('Get_items')?['body/value'], '}}')))
Select extracts out all the App Owners across the list items. This will allow us to iterate over each one to get their items and send an email. The expressions used are:
//From
xpath(outputs('XML'), '//root/value/AppOwner')
//Map
json(item())?['AppOwner']
Style HTML table is a Compose action that contains some CSS for styling the HTML table so it looks nicer in the email sent out.
<style>
table {
border-collapse: collapse;
}
table td,
table th {
border: 1px solid #ddd;
padding: 6px 20px;
text-align: left;
}
table th {
background-color: #1C6EA4;
color: white;
}
</style>
Apply to each iterates over each of the App owners. It uses the following expression to remove duplicate values so we only iterate over each App owner once.
union(body('Select'), body('Select'))
Filter array uses the output from Get items and checks to see if App Owner contains the current App Owner we are iterating over.
Create HTML table uses the output from Filter array (the items for the current App Owner) and maps out the fields we want to show. Below are the expressions used for each of the mappings.
//Application ID
item()?['ApplicationID']
//Application Name (uses the Title field in our SharePoint list)
item()?['Title']
//Domain (Need to get the value sinces it's a Choice field)
item()?['Domain/Value']
//App Owner(s)
join(
union(
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()')),
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()'))
),
', '
)
//Escalation Focal
item()?['EscalationFocal/DisplayName']
//Other fields
item()?['NAME_OF_YOUR_FIELD']
Escalation Focal Emails is a Compose action that retrieves each of the Escalation Focal emails that are related to the records in the current HTML table data. It removes duplication emails and joins them with a semicolon so we can use them in the CC field in our email.
join(
union(
xpath(outputs('XML'), concat('//root/value[AppOwner/DisplayName="', item()?['DisplayName'], '"]/EscalationFocal/Email/text()')),
xpath(outputs('XML'), concat('//root/value[AppOwner/DisplayName="', item()?['DisplayName'], '"]/EscalationFocal/Email/text()'))
),
';'
)
Send an email (V2) uses the output from Style HTML table and Create HTML table in the Body, and the output from Escalation Focal Emails in the CC field. It also uses the following expressions for the To field and the Display Name in the body.
//To
items('Apply_to_each')?['Email']
//Display Name (in the Body greeting)
items('Apply_to_each')?['DisplayName']
A couple of sample emails sent out are below.
Hi @grantjenkins ,
This is perfect solution. You're amazing!
The only change I need is here is records to be filtered as per Domain and not as per App_Owner column.
I managed to do that till HTML Table and ran the test output and bingo! Tables got created as per each Domain.
after filtering by Domain Escalation Focal Emails started failing.
Error:
Unable to process template language expressions in action 'Escalation_Focal_Emails' inputs at line '0' and column '0': 'The template language expression 'join(
union(
xpath(outputs('XML'), concat('//root/value[App_Owner/DisplayName="', item()?['DisplayName'], '"]/Escalation_Focal/Email/text()')),
xpath(outputs('XML'), concat('//root/value[App_Owner/DisplayName="', item()?['DisplayName'], '"]/Escalation_Focal/Email/text()'))
),
';'
)' cannot be evaluated because property 'DisplayName' cannot be selected. Property selection is not supported on values of type 'String'. Please see https://aka.ms/logicexpressions for usage details.'.
Below is how I would do this by Domain.
See full flow below. I'll go into each of the actions.
Get items retrieve the list items.
XML is a Compose that converts the data to XML (same as before).
xml(json(concat('{"root": { value:', outputs('Get_items')?['body/value'], '}}')))
Select retrieves all the Domains. Note that we use Domain Value here to get the actual value of the choice field.
Style HTML table is a Compose that contains some CSS (same as before).
Apply to each iterates over each unique Domain.
union(body('Select'), body('Select'))
Filter array filters on Domain Value to retrieve the items for the current Domain we are iterating over.
Create HTML table is exactly the same as before (no changes).
App Owner Emails is a Compose that retrieves a list of all the App Owner emails and joins them with a semicolon.
join(
union(
xpath(outputs('XML'), concat('//root/value[Domain/Value="', item(), '"]/AppOwner/Email/text()')),
xpath(outputs('XML'), concat('//root/value[Domain/Value="', item(), '"]/AppOwner/Email/text()'))
),
';'
)
Escalation Focal Emails is a Compose that retrieves a list of all the Escalation Focal emails and joins them with a semicolon.
join(
union(
xpath(outputs('XML'), concat('//root/value[Domain/Value="', item(), '"]/EscalationFocal/Email/text()')),
xpath(outputs('XML'), concat('//root/value[Domain/Value="', item(), '"]/EscalationFocal/Email/text()'))
),
';'
)
Send an email uses the output from Style HTML table and Create HTML table in the Body, the output from Escalation Focal Emails in the CC field, and the output from App Owner Emails in the To field. I also added Current item in the Subject, so it shows the current Domain.
Below are the emails that would be sent out for each Domain.
@grantjenkins thanks a ton again for your efforts.
Can you please provide the code you added here for App Owner(s). This is exactly the same step where I'm stuck from the very beginning 😂.
My flow is getting failed only for this step.
Below is the expression for getting the App owners. You may need to change the field name to suit what you have.
//App Owner(s)
join(
union(
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()')),
xpath(outputs('XML'), concat('//root/value[ID="', item()?['ID'], '"]/AppOwner/DisplayName/text()'))
),
', '
)
What is the error message you are getting?
Yes its all working. I was making mistake in actual column name on SharePoint List.
Thanks again 😀
@grantjenkins additional request please.
By any chance if you can help with Days Left column. Since it is a calculated column on Sharepoint it is giving value in decimals.
<Days_Left>-5.437500000000000</Days_Left>
Can we convert this value to Integer? I tried using Int(item()?['Days_Left'])
unfortunately it's not working.
What would you expect it to be? Converting to an integer will cut off the decimal places. Did you want to just remove the decimal places, or round up/down?
Alternatively, we could just have it formatted with 2 decimal places.
Let me know.
Yes. Since it is calculated date difference, so I just want to remove decimal places. not rounding off.
Hi @grantjenkins,
Did you get chance to look at number decimal issue?
xml output:
<Status>Overdue</Status>
<Days_Left>-6.43750000000000</Days_Left>
output should be only -6 days.
Try the expression below:
first(split(item()?['Days_Left'], '.'))
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages