Hi everyone,
So few months back I had designed a flow (Power Automate flow) that collects all users from a Microsoft Teams group (with headers in the excel sheet: Name, Email, Dates of the week) this file is created at the start of the week (i.e. Monday at 9:30 am IST) and a message is shared on the Teams channel that the file is being created for the week please enter your work mode for the current week (WFO - Work From Office and WFH - Work From Home).
But there were some issues like if a holiday comes in (like on Monday like for New year 1st Jan) in this case no user will login and fill in the timesheet (as it's a Holiday 😉) so in such cases I wanted the flow to fill it as 'Holiday'.
So my flow looks like this:
This flow creates an Excel which looks like this:
So I created a HolidayList excel which has all the list of holidays as per my region
So now I was thinking how to refer this (holiday list sheet) and if there is any date that is present and matches with one of the dates in the week (like 26th Jan is a Republic Day which is on Friday) so for that week on Friday the flow should add the value to all rows for that day (for all users) as 'Holiday'/ 'Holiday_name (Republic Day) Holiday'.
And the next thing that I was thinking of sending a reminder (at-least for two days like Tuesday,Wednesday: For users who have not filled the time sheet 'Please fill your work mode time sheet for the week' and next week (the previous week timesheet should not be editable for users)
So if anyone has any idea about this please let me know it would help and if any more information is needed do let me know.
Regards,
Sidhant.
Solved! Go to Solution.
Hi @BCBuizer ,
Thanks for the response I will try the approach that you have suggested. Before doing that I did check your point 1 wherein you did confirm that the expression is right only I need to remove the double quotes ("") for the value part and use single quotes (''), but that resulted in Invalid json message in Power Automate
So I replaced it with double quotes again and then there were no errors, then when I tried tested the flow it failed at the Compose action inside the loop
And when I checked in the OneDrive folder as well the file was created (the headers were displayed properly) but they had no values i.e.Employee Name, Employee email (which is because the compose action i.e. loop did not execute)
Anything that I have missed?.
Regards,
Sidhant.
Hi @BCBuizer ,
I did try the new approach wherein you suggested to add a 'Select' operation just before the loop like:
For the From: used this
{You had written: @{outputs('List_rows_present_in_a_table')}}
Then in Compose action used the following Expression:
"split(outputs('Header'),',')[0]" : "if(contains(join(body('Select'),','),split(outputs('Headers'))[0]),'Holiday','')",
"split(outputs('Header'),',')[1]" : "if(contains(join(body('Select'),','),split(outputs('Headers'))[1]),'Holiday','')",
"split(outputs('Header'),',')[2]" : "if(contains(join(body('Select'),','),split(outputs('Headers'))[2]),'Holiday','')",
"split(outputs('Header'),',')[3]" : "if(contains(join(body('Select'),','),split(outputs('Headers'))[3]),'Holiday','')",
"split(outputs('Header'),',')[4]" : "if(contains(join(body('Select'),','),split(outputs('Headers'))[4]),'Holiday','')"
//Here I have used double quotes on both sides as when I tried to use just single quotes for the value part it displayed invalid JSON message.
//In Flow (Actual Expressions)
{
"SNo": "@{variables('varCounter')}",
"Employee Name": "@{items('Apply_to_each')?['displayName']}",
"Employee Email": "@{items('Apply_to_each')?['email']}",
"@{split(outputs('Header'),',')[0]}" : "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[0]),'Holiday','')}",
"@{split(outputs('Header'),',')[1]}" : "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[1]),'Holiday','')}",
"@{split(outputs('Header'),',')[2]}" : "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[2]),'Holiday','')}",
"@{split(outputs('Header'),',')[3]}" : "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[3]),'Holiday','')}",
"@{split(outputs('Header'),',')[4]}" : "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[4]),'Holiday','')}"
}
And on Save it gave the following error message:
Is there anything that we might have missed?.
Regards,
Sidhant.
Was able to solve the issue it was due to:
Before:
"@{split(outputs('Header'),',')[0]}" : "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[0]),'Holiday','')}"
//It was Headers not Header:
"split(outputs('Headers'),',')[0]": 'if(contains(join(body('Select'),', '),split(outputs('Headers'))[0]),'Holiday','')'
So now I was able to save the flow but now was facing a new issue:
(I guess it might be the indexing that I was talking about in my yesterday's reply as [0] might refer to SNo: which is populated by varCounter), so I did make some modifications to the expression in the Compose action.
{
"SNo": "@{variables('varCounter')}",
"Employee Name": "@{items('Apply_to_each')?['displayName']}",
"Employee Email": "@{items('Apply_to_each')?['email']}",
"@{split(outputs('Headers'),',')[3]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[3]),'Holiday','')}",
"@{split(outputs('Headers'),',')[4]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[4]),'Holiday','')}",
"@{split(outputs('Headers'),',')[5]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[5]),'Holiday','')}",
"@{split(outputs('Headers'),',')[6]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[6]),'Holiday','')}",
"@{split(outputs('Headers'),',')[7]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[7]),'Holiday','')}"
}
So any idea what is going wrong (in both the approaches : 1st without the select action and the other with Select action) @BCBuizer
Regards,
Sidhant.
Hi @Sidhant_02 ,
I would suggest to only keep the dates in the header as per point 3. in my previous reply. It seems somehow the Sno key is duplicated.
Hi @BCBuizer ,
Something like this:
Updated:
{
"SNo": "@{variables('varCounter')}",
"Employee Name": "@{items('Apply_to_each')?['displayName']}",
"Employee Email": "@{items('Apply_to_each')?['email']}",
"@{split(outputs('Headers'),',')[0]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[0]),'Holiday','')}",
"@{split(outputs('Headers'),',')[1]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[1]),'Holiday','')}",
"@{split(outputs('Headers'),',')[2]}": "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[2]),'Holiday','')}",
"@{split(outputs('Headers'),',')[3]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'))[3]),'Holiday','')}",
"@{split(outputs('Headers'),',')[4]}": "@{if(contains(join(body('Select'),','),split(outputs('Headers'))[4]),'Holiday','')}"
}
But even after doing the changes:
Still facing the same issue.
Regards,
Sidhant
Hi @Sidhant_02 ,
It seems the second argument in the right set of split functions was missing:
{
"SNo": "@{variables('varCounter')}",
"Employee Name": "@{items('Apply_to_each')?['displayName']}",
"Employee Email": "@{items('Apply_to_each')?['email']}",
"@{split(outputs('Headers'),',')[0]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[0]),'Holiday','')}",
"@{split(outputs('Headers'),',')[1]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[1]),'Holiday','')}",
"@{split(outputs('Headers'),',')[2]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[2]),'Holiday','')}",
"@{split(outputs('Headers'),',')[3]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[3]),'Holiday','')}",
"@{split(outputs('Headers'),',')[4]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[4]),'Holiday','')}"
}
Hi @BCBuizer ,
I did the updated expression that you have mentioned in your latest response which is:
{
"SNo": "@{variables('varCounter')}",
"Employee Name": "@{items('Apply_to_each')?['displayName']}",
"Employee Email": "@{items('Apply_to_each')?['email']}",
"@{split(outputs('Headers'),',')[0]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[0]),'Holiday','')}",
"@{split(outputs('Headers'),',')[1]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[1]),'Holiday','')}",
"@{split(outputs('Headers'),',')[2]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[2]),'Holiday','')}",
"@{split(outputs('Headers'),',')[3]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[3]),'Holiday','')}",
"@{split(outputs('Headers'),',')[4]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[4]),'Holiday','')}"
}
So now there is no error but it generates the following file:
So here the Email and SNo are missing (not populated; as they are no longer present in the Headers action) & there additional 3 columns Column6,Column7 & Column8 and the user data is not populated (from the Teams group), also I had made one change to the 'Holidays.xlsx' that is mentioned 18/04/2024 as a Holiday :
so I expected for 18/04/2024 column to be populated with 'Holiday' but that did not happen. Is the date format in the Holiday.xlsx sheet correct?.
Regards,
Sidhant.
Hi @Sidhant_02 ,
If adding those columns back to Headers, please do so, but then update [0]-[5] to [3]-[7].
For the dates I see a difference in the date formatting for the month: 04 vs. 4
Hi @BCBuizer ,
After adding back the required Headers that are SNo, Employee Name, Employee Email and made the indexes change in the compose action:
{ "SNo": "@{variables('varCounter')}", "Employee Name": "@{items('Apply_to_each')?['displayName']}", "Employee Email": "@{items('Apply_to_each')?['email']}", "@{split(outputs('Headers'),',')[3]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[3]),'Holiday','')}", "@{split(outputs('Headers'),',')[4]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[4]),'Holiday','')}", "@{split(outputs('Headers'),',')[5]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[5]),'Holiday','')}", "@{split(outputs('Headers'),',')[6]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[6]),'Holiday','')}", "@{split(outputs('Headers'),',')[7]}": "@{if(contains(join(body('Select'),', '),split(outputs('Headers'),',')[7]),'Holiday','')}" }
The file was generated properly only the Holiday was not being populated, you mentioned the difference of 04 vs 4 so for single digit dates like 9th April was Gudi Padwa even if I tried using 04 it took 4 as final o/p in the sheet
and when I checked the inputs after reading the HolidaysList it was something like this
(I also had added tomorrow's date as a holiday to test if Holiday is populated or not)
Regards,
Sidhant.
Hi @Sidhant_02 ,
In the Excel file, try to format the Date column as text instead of a date. I think that should resolve the issue.
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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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