Hi Everyone,
I have a simple share point flow. There are 2 lists. The "style list" has a style number column which should have a unique number. ( enforced unique values) . The second list is "style_color" list which gets the style number from "style list" by a lookup.
We have some additional columns in "style list" which we get these fields by a "get item" action in a flow. Flow looks like below.
I had also added a trigger condition to avoid loops. If the value of trigger column is Yes then the flow runs and after this run it changes the trigger column to No. So this is like a manual trigger.
This flow worked perfectly in last 1,5 years. But recently the flow is failing as below.
Because I can not see and select the get item list id in the dynamic content. Now all our operations are stopped as the flow does not work. I have a case with microsoft about this problem but no improvement in last 3 weeks. Flow team sent me to share point team but no progress so far.I could not talk with anybody in microsoft support team who knows both sharepoint and flows 😞 It looks like this is a bug or something is corrupted as the flow has been working perfectly in last 1,5 years and we did not change anything. Now it does not work. Did anyone have such a problem ? Can you help me ?
Thank you !!!
Deniz Ozgentas
There are a couple options that might provide a workaround. First, did you check the output from a previous run to make sure the column you need is included in the output of the trigger? If it isn't, then check the view settings under the advanced settings for the trigger and select use all columns or a view that explicitly includes that column.
Once the column is showing in the output of the trigger you have two options if it still doesn't show in dynamic content. First you can add it to a compose or variable earlier right after the trigger. The dynamic content list gets filtered pretty heavily and that is often why you can't see the dynamic content you need when you need it. The other option is to hand code the JSON for the dynamic content in the function tab. That would look something like the following
outputs('When_an_item_is_created_or_modified')?['Style_PO_ID']
Hi,
Thank you for your quick feedback. The outputs of the trigger is as below. It does not show columns existing in STYLE_COLOR list. I also checked the previous successful runs of the same flow and all the columns were listed in the outputs of the trigger.
I tried to add a compose or JSON after trigger ( before get item ) but those did not work either. The result is failed checks as below
Once again my get item list dynamic content is missing. Therefore can not select get item LIST ID from dynamic content.
However get item dynamic content still shows in update item action. I guess if I can not select get item ID then get item dynamic content were not supposed to be shown in update action ? Flow does not run anyway. This was perfectly working until 2 weeks ago ?
Thank you !
If the trigger is based on the style list then there values from the style color list won't be there. You need to use the value for whatever column is the reference between the two lists. That would be the Style number. I would also assume the style number isn't the ID from the Style list. If that is the case then you'll need to use a Get Items, not a Get Item.
Hi,
thank you for your reply. Yes you are right, I need to select the style_po id from STYLE list in get item action. STYLE_COLOR list selects the style_po ( which is unique in STYLE list) from STYLE list. This way we can see the columns of the get item ( STYLE list) in the dynamic contents and add to UPDATE ITEM action. Now the only problem I have is "when an item is created or modified" flow with trigger condition (@equals(triggerBody()?['TRIGGER_x002e_'],True) does not trigger.
This is the trigger condition
This is the error message I am getting
This listed under failed checks as below
it says bad request , status code 400.
I also tried to make a simple new get item flow with the same conditions and it worked .
Could it be something related with connectors etc. I am nor experiences with the admin functions maybe microsoft can solve this ?
https://docs.microsoft.com/en-us/power-automate/triggers-troubleshoot#sharepoint-trigger-issues
thank you for your help !
For the moment remove the trigger condition and add it to a Compose statement using the expressions tab. That will let you see the values being evaluated and the result.
Hi,
I just removed the trigger condition and tried to run the flow. It did not work. Same error. Failed check
I also tried to add a compose action right after trigger
added below condition in expessionstab
@equals(triggerBody()?['TRIGGER'],True)
But it says expresion is not valid. ? I guess i am doning something wrong ? do you mean the above ?
In the meantime microsoft team is working on the related sharepoint list and they asked me to reduce total number of lookup columns to 10. It did not help either 😞
i do not understand why a flow working for 1,5 years without a problem and not working now even we did not change anything in the list structure or flow details ?
thanks
The code you put in the Compose isn't the same as what you had in the Trigger condition. Also, if you have a substantial number of Lookups you should be using a view to limit the number of columns being returned by the trigger. To answer your question of why it breaks now after running for over a year, there are two options. One, someone may have made a change to the underlying list. For example adding an additional Lookup column. Or Two, MS is continually refining the connectors to improve performance. It may be that one of those changes broke the way you were using the list.
If you removed the Trigger condition and still got an error then the flow did run and the problem wasn't with the Trigger. In the flow run itself what action is throwing the error?
Hi,
Thank you for your reply.
Actually the the code in compose is same as the condition in the trigger. The screenshot does not show the Beginning part of the code. it is below
@equals(triggerBody()?['TRIGGER'],True)
The trigger of the flow is "when an item is created or modified" in the list. Now I removed above condition from the flow trigger, It triggers as below. It gets all the get item columns from STYLE list. But Fails at update item ( meaning can not go to other steps ?) .
On the other hand the flow without above additional trigger condition is not usable as it gets into a infinite loop and stops at the end.
My total number of lookup columns is 10 and below MS max 12 limit! MS support teams can not solve this too.
I spend 2 weeks with flow team and they passed me to sharepoint teams and after addtional 2 weeks they passed me to flow team again. This is very slow and frustrating process!!!
This is very dissapointing when you move all your company date to sharepoint and using the flows and MS could not solve this problem in last 4 weeks !!
thank you for your help.
Your original screenshot says the field for the trigger condition is ['TRIGGER_x0002e_']. That is not the field name you used in the Compose. Are you sure the field is just TRIGGER? Not TRIGGER_x0002e_ or TRIGGER_Yes_No which I see in the error message?
For the Update Item when the trigger condition isn't in place what field are you using for the ID? Would you provide a screenshot of the Update Item action?
Hi,
Thank you for your reply. I just checked the field name used in trigger condition and in the TriggerBody dynamic content. You are right! For some reason the filed name in dynamic content is TRIGGER_YES_NO so i added this field name in trigger condition as below and the trigger condition worked. ( I do not know how it was changed to TRIGGER_YES_NO ?? )
Now i can trigger the flow with condition without having a loop. It gets the values from STYLE list. But it fails in next update item action as below. So flow does not perform the other steps.
it says BAD REQUEST STATUS 400
thank you !
Can you provide a screenshot of the Update Item action and how its configured? Something in the way its configured is incorrect.
Hi,
please see the structure of the update item in the flow. id is the list ID of the triggerbody list ID which is STYLE_COLOR list.
Actually now this update action is performing perfectly as before and completed all the actions. But flow does not go to next step
I got below error message
I don't really see anything wrong, but I did notice that you haven't filled in the Title field and that its no longer displaying as a required field. I would recommend not making those kinds of changes to system level settings. They can often have unexpected side effects. Other than that I don't have any other suggestions on what may be wrong with the flow. It appears pretty straight forward. But given the confusion and unexpected changes to the trigger condition column name I would suspect it has something to do with changes that have been made to the underlying list. You may have to remove and re-add some of the actions to clear up any corrupted metadata. Or worst case scenario start over with a new flow.
Hi,
Thank you for your reply. I added title value in one of the raws and tried to run the flow but it still fails in the update item action after performing all necesseary actions there. As you said my field name in STYLE_COLOR list is TRIGGER in the list settings as below.
However when I select it from dynamic content it shows as TRIGGER_YES_NO ?? Also existing flow which triggers with condition works with below condition which is TRIGGER_YES_NO
@equals(triggerBody()?['TRIGGER_YES_NO'],True)
I guess field name is supposed to be be same but it is triggering ??? maybe there is a corruption with the list ?
My actual flow is a very long one with many conditions and actions. It would take long time to create the same but of course it is possible as I have been working on this problem in last 5 weeks ! Also I tried to create a new flow from scretch. you can see below. The trigger condition is same as above.
The flow does not trigger. it says there is a problem with the trigger of this flow
and report shows as below in failed checks
It looks like I am not able to create the flow from scretch 😞 on the other hand STYLE_COLOR list has about 1000 raws and there is another list that gets the items ( same way with GET ITEM ) from STYLE_COLOR list. this list has about 1500 raws. So I have to fix this and use the existing STYLE_COLOR list data. do you think Microsft engineers can fix this ? Their flow team said this is related with the list. sharepoint team said there is nothing wrong with the list. now they passed me to flow team again but i am not sure if this is a flow problem as all the problem is related with STYLE_COLOR list. My other flows ( same structure, pretty basic) about other lists works fine.
All our activities are almost stopped as we depend on these lists and flows and this is really frustrating as microsoft is very slow to take action on these. The support staff do not know details of the subject. They could not make analysis anywere close to you have done so far ! thanks !
thanks for your suggestions !
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