Hello,
I hope you are all fine. I'm writing a post because I'm having a problem with Power Automate Flows.
My goal is to synchronize two SharePoint Lists. I've created two SharePoint Lists to assign roles to two categories of users. Some users can edit columns 1 and 2, while admins can edit columns 1, 2 and 3. My aim is to synchronize these lists so that changes in List 1 are automatically reflected in List 2. In addition, user 2, with extended rights, should be able to correct user 1's entries.
I've followed the following tutorial, but when I create two flows with this structure, they work fine but enter an infinite loop... I was wondering if you have a solution to solve this problem please because itโs been several days that I am not able to fix the issueโฆ
โ
Could you please help me because I really donโt know how to solve thisโฆ
Thanks in advance for your time and help.
Best regards,
Sarah
Solved! Go to Solution.
Hi @Sarahnt,
Yup, of course this solution works when you can update SystemUpdateVersion field at the same time you change other fields, but for attachment you use another action which doesn't allow you to also update that field value.
The only way I see is to replace above solution by just adding following trigger condition: @not(equals(triggerbody()?['Editor']?['Email'],'PowerAutomate@contoso.com'))
Where "PowerAutomate@contoso.com" is the email of the user with which you designed your flow. Hope you're using a service account because if you're using your personal account it will not work when you create or modify the list items but will with anyone else.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Hi @Sarahnt,
I guess both flows use same "When a item is created or modified" trigger, and you enter infinite loop because when you update list 1, flow update list 2 which trigger second flow to update list 1, and so on...
I've designed this solution to avoid entering infinite loop while updating a list monitored by "When a item is created or modified" trigger : Solved: No loop SharePoint update item trigger - Power Platform Community (microsoft.com)
[Edit] This solution was designed to avoid loops when updating the list in the flow triggered by this list. But it will work the same for your both flows. When flow 1 (triggered by list1) update list 2, update SystemUpdateVersion in list 2 so it will not trigger second flow. Do the opposite for second flow.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Hi @SamLed thank you for your answer and for helping me. I edited my flow as you said but the issue persists, I still do have an infinite loopโฆ
My flow is as follows:
1. Once an item is edited or created - List 1 (I added the following expression as trigger condition in trigger settings as mentioned in your tutorial: @not(equals(triggerBody()['SystemUpdateVersion'],triggerBody()['{VersionNumber}']))
2. Get the items - List 2
3. Message/Compose (expression: formatNumber(add(float(triggerOutputs()?[โbody/{VersionNumber}โ]),1),โF1โ)
4. Condition (expression: length(outputs(โ Obtain_items_List_2โ)?[โbody/valueโ]
4.1. Create item - List 2
4.2. Update item - List 2
I have an error at step 1 with the condition @not(equals(triggerBody()['SystemUpdateVersion'],triggerBody()['{VersionNumber}']))
do you know why I have an error with this condition even though I created a text column named SystemUpdateVersion in my two lists?
Thank you in advance for your help
Hi @Sarahnt,
What is the error raised ?
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Hi @SamLed, It says that the field SystemUpdateVersion doesn't exist even though I created it...
Here is the message details: The template language expression 'not(equals(triggerBody()['SystemUpdateVersion'],triggerBody()['{VersionNumber}']))' cannot be evaluated because property 'SystemUpdateVersion' doesn't exist, available properties are '@odata.etag, Sports etc... (others fields of my list)
Can I please share you my screen @SamLed and show you my flows please because I really do not understand why it doesn't work... It would be really kind of you because I really do not know how to fix this issue. I tried many many times but it didn't work
Hi @Sarahnt,
That will be useless, I mean, as you added the column after flow design, not sure trigger's has detected change. Give me a minute, trying to figure how to fix that.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Thank you for your help @SamLed. I think by showing you my screen maybe you will see if I didn't configure something well concerning the solution you proposed. Can't I show you quickely please??
Hi @Sarahnt,
No need, I've reproduced the issue by creating a SystemUpdateVersion2 column and modified my trigger condition. I got the same error and looking for a fix.
______________________________________________________________
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Hi @Sarahnt,
Ok, just figured out that was not any list schema refresh issue, I've tested original flow I used to test the solution and it also failed, it seems something changed on how Power Automate deal with trigger outputs since I've written the article.
Give a try with this trigger condition: @not(equals(triggerOutputs()?['body/SystemUpdateVersion'],triggerBody()['{VersionNumber}']))
I've replaced triggerBody()['SystemUpdateVersion'] by triggerOutputs()?['body/SystemUpdateVersion'] and it worked again on my side.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Hi @SamLed thank you very much for testing and helping me.
It unfortunetly doesn't work in the case where you synchronize the update of attached files.... The loop goes on forever
Hi @Sarahnt,
Yup, of course this solution works when you can update SystemUpdateVersion field at the same time you change other fields, but for attachment you use another action which doesn't allow you to also update that field value.
The only way I see is to replace above solution by just adding following trigger condition: @not(equals(triggerbody()?['Editor']?['Email'],'PowerAutomate@contoso.com'))
Where "PowerAutomate@contoso.com" is the email of the user with which you designed your flow. Hope you're using a service account because if you're using your personal account it will not work when you create or modify the list items but will with anyone else.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Did you keep both of the trigger conditions? Because by my side the loop persists if I only put@not(equals(triggerbody()?['Editor']?['Email'],'PowerAutomate@contoso.com')) ๐
It may not work because I'm using a personal account... How can I fix this please?
Hi @Sarahnt
Nope, use only last one.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
But do you use same account to edit flow and to update items ? it will not work, you have to use an account for your flows and another for updating items ๐
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Yes I do use the same account. Does it mean that I have to create an environment in admin.powerplateform.microsoft.com? (because I don't have any it's empty and I don't have the permission to create one)
Ok, that's not a good practice, to my customers I always advice to create a service account for power automate and design flow with it. I have same practice for my dev tenant.
You'll have many advantage:
- Dedicated mailbox
- No need to change owner when leaving organization (when they don't forget to change before deleted account, already saw that)
- Usually that account can have high permissions, regular users shouldn't have
[Edit] for your testing purpose, as you've got only one account, you have to ask somebody else to modify items and there will be no loop. Or if you can, create another account to test.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
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