Hi all,
I have a bit of an issue with a flow I'm building to create outlook events that we can later follow up on and log whether they were successful and add notes and whatnot.
Everything to create the item is working well, but the problem is on my update list item step at the end where I am adding the outlook event ID in case the event needs to be altered that could still be done from the list using the ID to find it.
I have a people picker column that allows people only / multiple selections for selecting trainees. Each trainee gets added to the invite and their manager is pulled and added as optional to the invite to keep them apprised of the situation.
On my update list item action, I have to add the value for for these trainees because I have the field as required. I am initializing an array variable an applying to each appending the user claims variable. Upon completion, I see outputs in the flow report, but the field gets cleared out in my list.
I have this same solution in place elsewhere but not for a people picker, just a regular multi-select choice column, and those work fine, so I'm wondering if anyone has any ideas. I have tried claims and I have tried the email value in the variable, but same issue persists.
Thank you for your time.
Solved! Go to Solution.
Instead of the Switch function I'd recommend creating a JSON object instead and using an expression. I would recommend creating a new flow for you to test out the concept first before adding it to your current flow. I demo this concept in this section of one of my tutorials.
Add a Compose action with your dynamic content key. Insert opening and closing curly brackets. Between the curly brackets enter a line for each content pair.
In your case, the location would be on the left (before the colon) and the email address(es) would be on the right. If you have multiple email addresses ensure you have a semi-colon separating each.
{
"Location 1": "email1@email.com;email2@email.com"
}
There should be a comma after each line except for the last line.
Add another Compose action to store a testing value (aka Location in your case). Tip: Always rename your actions especially if you have multiple instances of the same action in your flow. It'll help to keep things organized.
This Compose action is optional, you can insert the value right into the expression. However to help you better understand what's going on, I recommend you use a Compose action. You will replace this with dynamic content from your actual flow. Keep in mind this value must match the text exactly as you have it in your key. Enter any value for testing purposes.
Add one more Compose action to store an expression. Insert a question mark and square brackets.
In between the square brackets insert the output from the Compose action above.
Go to the start of the expression by pressing the up arrow key. Insert the output from the Compose action with the JSON object.
This expression will output the value on the depending on what value is inserted into the square brackets of the expression.
Run a test. Review the outputs. You can adjust the value in the Compose action to another value and run another test. Ensure the output is what you are expecting.
You can copy these actions int your current flow and insert the appropriate dynamic content (location value in your case) into the Compose action that is holding the value.
----
It's unclear to me the reason you have initialized these two variables:
When updating a multi-choice person column. The array structure that is expected is
[
{
"Claims": "emailaddress1@email.com"
},
{
"Claims": "emailaddress2@email.com"
}
]
If the Trainee's dynamic content is a multi-person field, you can use a Select action. In the From field, insert the multi-person dynamic content.
In the Key field, enter the word Claims. In the second value field insert the multi-person email dynamic content.
Run a test. This is what the output should look like.
You can take the output from the Select action and insert it into the multi-person column field of your Update Item action.
The Select action outputs an array. You can use the output of the Select action in an Apply to Each action. The Compose action is optional, however it can help with troubleshooting. I'm using it to output the current email being looped through.
You'll need to insert an expression:
item()?['Claims']
Insert the Get manager (V2) action.
Add an Append to Variable action to collect the display name and email address of each manager. The format is the same as the JSON object.
Add a Compose action outside of the Apply to Each action to output the variable.
Run a test. Review the outputs.
Use a Select action to collect the Email Addresses only. In the Fro field, insert the output from the Compose action above (or the variable).
Insert an expression.
item()?['Dynamic Content Key']
Replace the text in blue with the appropriate key. In this case, Email. You'll need to repeat this for the Display Name.
Insert a Compose action and use the join() function to convert the email from an array to a string.
Run a test. Review the outputs.
I would recommend adding Scope actions to your flow to keep it organized. The Scope action is optional however you can quickly collapse multiple actions with a single click.
@LoufromNH It's hard to offer any recommendations without seeing how your flow is laid out. Upload a screenshot of your flow in edit mode and the error you are receiving, it would help to provide more insight.
In the meantime, you might be interested in this YT Tutorial:
How to Handle Multi-Person SharePoint Item Notifications in Outlook and MS Teams with Power Automate
Do you want to know how to send an email to all users assigned to a SharePoint item? If so—this Power Automate tutorial is for YOU 🫵.
In a different YouTube tutorial I covered how to build a Power Automate flow that sends a single email to each user with the tasks assigned to them.
However, that tutorial only covered a scenario where each task is assigned to a single user. What if your task is assigned to more than one user?
In this Microsoft Power Automate tutorial I’ll cover how to create a flow that is triggered by selecting an item. This automation will send an email to all assigned users for the selected task. I’ll also show you how to adjust your flow so that you can send a message in Teams. Then I’ll show you how to collect a list of unique users that have been assigned to multi-person tasks. Using this concept, we’ll edit the flow from the previous tutorial so that it works with a multi-person column.
IN THIS VIDEO:
✅ How to trigger a flow from a selected file
✅ How the multi-person column data outputs
✅ How to use the Select action to get all assigned to users of a SharePoint item
✅ How to use the Join action to convert an array of email addresses into a string
✅ How to send a single email to all assigned to users of a SharePoint item
✅ How to send an email to each assigned to user of a SharePoint item
✅ How to send a Teams message to each user assigned to a SharePoint item
✅ How to return a list of unique users from the multi-person column in a SharePoint list
✅ How to use a Filter Array action to return all SharePoint list items assigned to each user
✅ How to group Power Automate actions together with the Scope action
✅ How to edit a previous flow
Hello, I will attach a few photos. The thing is I'm not getting any errors. I was but I've cleared them and now am observing this strange behavior. My thinking is that the values aren't validating for the people picker column so they end up just not saving, but since an overwrite was attempted the old values aren't available anymore either.
@LoufromNH It would provide more insight if you could click on all actions to expand them. It's hard to understand the logic when the actions aren't expanded.
Hello,
The following are seperate pictures, but they are in order. Nothing is missing except a few more Switch options off to the sides, but they just take the value of the list dropdown for room name and append a variable with the room email so I can use it to book the room.
But, there are no errors to show, unfortunately:
Thank you for looking.
Instead of the Switch function I'd recommend creating a JSON object instead and using an expression. I would recommend creating a new flow for you to test out the concept first before adding it to your current flow. I demo this concept in this section of one of my tutorials.
Add a Compose action with your dynamic content key. Insert opening and closing curly brackets. Between the curly brackets enter a line for each content pair.
In your case, the location would be on the left (before the colon) and the email address(es) would be on the right. If you have multiple email addresses ensure you have a semi-colon separating each.
{
"Location 1": "email1@email.com;email2@email.com"
}
There should be a comma after each line except for the last line.
Add another Compose action to store a testing value (aka Location in your case). Tip: Always rename your actions especially if you have multiple instances of the same action in your flow. It'll help to keep things organized.
This Compose action is optional, you can insert the value right into the expression. However to help you better understand what's going on, I recommend you use a Compose action. You will replace this with dynamic content from your actual flow. Keep in mind this value must match the text exactly as you have it in your key. Enter any value for testing purposes.
Add one more Compose action to store an expression. Insert a question mark and square brackets.
In between the square brackets insert the output from the Compose action above.
Go to the start of the expression by pressing the up arrow key. Insert the output from the Compose action with the JSON object.
This expression will output the value on the depending on what value is inserted into the square brackets of the expression.
Run a test. Review the outputs. You can adjust the value in the Compose action to another value and run another test. Ensure the output is what you are expecting.
You can copy these actions int your current flow and insert the appropriate dynamic content (location value in your case) into the Compose action that is holding the value.
----
It's unclear to me the reason you have initialized these two variables:
When updating a multi-choice person column. The array structure that is expected is
[
{
"Claims": "emailaddress1@email.com"
},
{
"Claims": "emailaddress2@email.com"
}
]
If the Trainee's dynamic content is a multi-person field, you can use a Select action. In the From field, insert the multi-person dynamic content.
In the Key field, enter the word Claims. In the second value field insert the multi-person email dynamic content.
Run a test. This is what the output should look like.
You can take the output from the Select action and insert it into the multi-person column field of your Update Item action.
The Select action outputs an array. You can use the output of the Select action in an Apply to Each action. The Compose action is optional, however it can help with troubleshooting. I'm using it to output the current email being looped through.
You'll need to insert an expression:
item()?['Claims']
Insert the Get manager (V2) action.
Add an Append to Variable action to collect the display name and email address of each manager. The format is the same as the JSON object.
Add a Compose action outside of the Apply to Each action to output the variable.
Run a test. Review the outputs.
Use a Select action to collect the Email Addresses only. In the Fro field, insert the output from the Compose action above (or the variable).
Insert an expression.
item()?['Dynamic Content Key']
Replace the text in blue with the appropriate key. In this case, Email. You'll need to repeat this for the Display Name.
Insert a Compose action and use the join() function to convert the email from an array to a string.
Run a test. Review the outputs.
I would recommend adding Scope actions to your flow to keep it organized. The Scope action is optional however you can quickly collapse multiple actions with a single click.
I will give this a try and let you know.
Thank you for the detailed help.
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