Hi there,
I am strugling to find a way to build a working flow for below scenario.
I have to build a flow which finds duplicates in a Sharepoint list that have more than 5000 items based on Concatenate value between 3 columns (Title, Request type, Title2) and then update column Duplicate with value Yes.
Thank you for your help!
Solved! Go to Solution.
@royg I'm curious how Xpath would help with that. Maybe you can elaborate.
For performance I would concatenate the strings in a select action and then filter the array that the select action returns and count those rows.
That'll be faster than the cascading filter actions.
@SuperPowerUser1
I thought you would have to handle all the existing items in the SharePoint list.
If that is not the case you could (and should) do an odata filter on the get items action and only return the items that match all three fields. If that array has more than one items, you should update the row and mark it as a duplicate. However, that will not have any impact on your exisiting rows.
There are a few ways to go about this.
One way would be to use the get items action to get all the items of the list.
Then loop through the items and use a filter action on the list with title, then filter that for request type and then filter that for title2. Then check if length is greater than 1, if yes, update item column duplicate yes, in not,then set the duplicate column to no.
It will take some time, but it'll do the trick.
Hi @SuperPowerUser1,
As mentioned by @schwibach, this is a complicated scenario where you may have to iterate all the items in your list. If that flow runs too often (for example on a scheduled basis, it can get tagged as causing poor performance and eventually stopped.
what you could do to improve performance is use XPATH to count the occurrences of items with the same key (the concatenation of Title, Request type and Title2) but different ID. With that array filtered to only items with duplicates greater than 0, you can iterate probably far less items and modify them, or better yet, use Batch action to update them as duplicates. Note that you need to implement logics to locate items that were tagged as duplicates but are no longer (since they were either changed or their duplicates were removed) and tag them as non duplicates. Again, it's better to use Batch updates for that.
You can also consider handling the On item created/modified event to count duplicates of the current item and set its field respectively. If you do that than most of your items will have the correct value, but you'll need to fix it using a daily run to handle deleted items.
Hi @royg
Sounds like a very complicated task 🙂
I have never used XPATH or batch processing before so i will have to do more research on these actions.
The flow will run When an item is created so this will be quite often.
I was hoping there is a more simple way to achieve this. Will also try the solution suggested by @schwibach to see what is the performance.
Thank you!
@royg I'm curious how Xpath would help with that. Maybe you can elaborate.
For performance I would concatenate the strings in a select action and then filter the array that the select action returns and count those rows.
That'll be faster than the cascading filter actions.
@SuperPowerUser1
I thought you would have to handle all the existing items in the SharePoint list.
If that is not the case you could (and should) do an odata filter on the get items action and only return the items that match all three fields. If that array has more than one items, you should update the row and mark it as a duplicate. However, that will not have any impact on your exisiting rows.
Again, I agree with @schwibach,
When handling the Create item event, you definitely need to use OData filter to query all items with the same 3 values + unequal ID. The returned items + the newly created item need to be updated as duplicates.
As @schwibach mentioned, this won't update existing duplicates and moreover, this doesn't handle the changes in any of the 3 fields in existing items (this can create duplicates or remove them) and removal of items (which can also remove duplicates).
Using XPATH will allow creating a filtered array of all items that currently have duplicates without iterating the items:
concat(item()?['Title'],item()?['Requesttype'],item()?['Title2'])
xml(outputs('Compose_XMLPrep'))
xpath(outputs('Compose_XML'), concat('count(//root/array[not(ID="', item()?['ID'], '") and VALUE="', item()?['VALUE'], '"])'))
The Filter array results are all the duplicates in your list. Now you can use the Batch update process as documented here:
But this is half of the process. You still need to get all items that were marked as duplicates and are no longer duplicates (that means they have IsDuplicate = TRUE but they don't exist in the filter results). I won't add that here but if you need help with that, reach out and I'll try to assist.
Hope this helps.
There are ways to find duplicates without any xpath or looping:
https://powerusers.microsoft.com/t5/Power-Automate-Cookbook/Find-and-Remove-Duplicates/td-p/2191403
(I have recently built even more efficient processing steps than those in the video. It’s included in the solution package import.)
_____________________________________________________________________________
Subscribe to my YouTube channel
Two ways of checking for duplicates:
Select creates an array of 5000 random items
1. (Left branch)
Select 2
From:
range(0, length(body('Select')))
Map:
addProperty(
body('Select')[item()],
'Duplicate',
or(
and(
not(equals(item(), 0)),
contains(take(body('Select'), sub(item(), 1)), body('Select')[item()])
),
contains(skip(body('Select'), add(item(), 1)), body('Select')[item()])
)
)
2. (Right branch)
Compose
xml(json(concat('{"Root":{"Item":', body('Select'), '}}')))
Select 2
From:
body('Select')
Map:
addProperty(
item(),
'Duplicate',
greater(
xpath(
outputs('Compose'),
concat('count(//Item[Title="', item()['Title'], '" and RType="', item()['RType'], '" and Title2="', item()['Title2'], '"])'
)
),
1
)
)
Result
Both branches result in the original array with an additional property that indicates a duplicate
{
"body": [
{
"Title": "Title-19",
"RType": "RType-213",
"Title2": "Title2-9",
"Duplicate": false
},
{
"Title": "Title-5",
"RType": "RType-179",
"Title2": "Title2-6",
"Duplicate": false
},
{
"Title": "Title-22",
"RType": "RType-303",
"Title2": "Title2-2",
"Duplicate": false
},
{
"Title": "Title-11",
"RType": "RType-106",
"Title2": "Title2-7",
"Duplicate": false
},
...
where the left branch is slightly faster
Thank you all!
I have build the flow today as @schwibach suggested.
Odata filter on Get items matching the 3 columns.
Then check if the lenght of the output array is greater than 1.
If it is, then update the column Duplicate to Yes.
It is updating only the newly created item but it is what i was trying to achieve anyway.
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