I have a flow that uses data from a Sharepoint List to send out an email from a shared mailbox when there is a change in the Status column of the list. When the recipient of the email responds, I simply want to update that specific Sharepoint list item.
So I've built a second flow for incoming emails that uses the Condition of checking the Outlook Conversation ID against the "Conversation ID" captured in the original Sharepoint list item to determine whether or not to update. Unfortunately when it finds the condition to be true it does an Update Item to all items in the list.
I am pretty sure it is because I am using "Get Items" to check for the matching Conversation ID instead of Get Item (which is not possible initially) and so the system is then doing an "Apply to Each" across all items. Attached is a screenshot of my flow set up.
I have also tried numerous variations including initializing and setting variables, filter arrays, and more. I also have had a sneaking suspicion a few times that the email sent out from the flow, may have a different Conversation ID, but thus far - when I include the ConvID in the email body, I am seeing it is the same as what comes back in with the email reply. I'd be very keen and grateful to get some guidance on the best method to achieve this.
Hey
I suggest you simply use a filter query the Get items action to only get the items back you want. Then you can use the Dynamic content ID from that action to update the item. You don't need the "Get item" action.
Basically like this:
Filter Query in the Get items action should look something like this:
ConversionId eq '@{triggerOutputs()?['body/conversationId']}'
You have to use the internal name of the SharePoint column... so if your SharePoint column is called "Conversation Id", it might be "ConversionationId" or "Conversation%20Id" or something like that... Here's a guide on how to find the internal name of your column: https://sharepointstuff.com/2022/02/09/find-internal-column-name/
Cheers
If you had a space in your column then you would use _x0020_ instead of %20.
Conversation_x0020_ID eq '@{triggerOutputs()?['body/conversationId']}'
Thanks for the reply but I still get the same error. Meanwhile I have handled all this with a filter array and think I am making some progress - only remaining problem is if I use the Item ID from Get Items - it goes and updates every item in the SharePoint list, rather than the actual Item I want to update. Not sure if this is a consequence of my Filter or the fact I am choosing the ID from "Get Items". Attached are some screen captures
The reason it's not working correctly is that you filter the results using the Filter array, but then just use the output from the Get items action which includes all items. You would need to use the output from the Filter array in your Apply to each.
This is how I would build your flow. I think you just need to confirm what the internal name is for your Conversation ID column and the Submission Status choice column.
See full flow below. I'll go into each of the actions.
I've used When a new email arrives, but would be the same for When a new email arrives in a shared mailbox.
Get items has two conditions. One for the Conversation ID and one for the Submission Status which you had within your Apply to each before. This should return only the item you need to update.
ConversationID = '@{triggerOutputs()?['body/conversationId']}' and SubmissionStatus ne 'NEW'
Apply to each will iterate over the items returned from Get items. In our case it should only be one item, so the Apply to each will only run once.
Update item would use the ID from Get items and whatever other fields you need, including setting your Submission Status to UPDATE.
To check the internal names of your columns, go into the List settings, then click on your column. It will show the internal name at the end of the URL as shown below.
Thank you very much - I do think this makes sense and does get me closer to the solution but the query itself is still failing to function (see attached). Even when I simply run the query against only one field (say ConversationID) it fails. One the matter of my "Submission Status" column, that is a choice column which may be the reason that needs a filter array vs a query. I have simplified its name to merely "Status" to avoid any naming convention issues which may have been related to a two word column name
After further research, I am seeing that because my ConversationID field is a Multi-line text field and because my Status field is a choice field, the Filter Query in "Get Items" is expected to fail. It seems the best route is using Filter Array to ensure I get the appropriate item, but I welcome any recommendations anyone may have.
The Status Choice field would work as expected in the Filter Query of Get items. However, you would then need to use a Filter array to further filter on the ConversationID since it's a multi line of text column.
See full flow below. I'll go into each of the actions.
Get items only contains the filter on the Submission Status column. Just confirming this is the condition you want - won't bring any items back that are set to NEW.
SubmissionStatus ne 'NEW'
Filter array check to see if the ConversationID column contains the Conversation Id from the email.
Apply to each iterates over each of the items returned from the Filter array.
Update item uses the following expression to get the ID of the current item we are iterating over.
item()['ID']
Hello,
Sorry for going MIA on this, but got pulled into other initiatives and this fell to the back burner. I have implemented the above solution yet it still fails - below is the error message I get. Is it potentially due to the ConversationID column being a multi-line column?
Error Message:
"The field 'ConversationID' of type 'Note' cannot be used in the query filter expression."
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