cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Relloy
Regular Visitor

Problem with updating a Yes/No SharePoint column

Hello,

I am very new to power automate so please forgive any lack of common knowledge relating to this issue. 
The functionality of the flow is to trigger when a News Post on a SharePoint is created/modified (the post gets saved in SitePages folder by default). It will then post a message on a teams channel and then it should turn the "Toggle" Column to "No" (False). The only part currently I have problem with is changing the Yes/No column after the post. 

Relloy_0-1691592621726.png
This is currently what I have, to explain the 3 HTTP requests part they are all POST requests. I was following the steps I found online by someone else with similar needs (Solved: Updating SharePoint Page content SharePoint API - Power Platform Community (microsoft.com) ):

POST request with checkout method ( _api/sitepages/pages(@{triggerOutputs()?['body/ID']})/checkoutpage )
POST request to edit "Toggle" column with SavePage method ( _api/sitepages/pages(@{triggerOutputs()?['body/ID']})/SavePage )
POST request with publish method ( _api/sitepages/pages(@{triggerOutputs()?['body/ID']})/Publish )

 

When running the flow by creating a new file, the default "Toggle" value is "Yes" (True). It seems to run for several minutes stuck on the SavePage method, reporting a Bad gateway and retrying a few times. It also seems to also spawn a new instance of the flow trying the same thing. 

Relloy_1-1691593381478.png

 


I am not sure where to go from here, I attempted without the checkout and publish methods but I always get a error "We cannot save your changes because a site member has ended your editing session." I do not believe a delay would help and I would rather not delay the trigger if I can help it. 

I am open to any other workarounds to simply edit a single column of a New Post that resides in SitePages.

Any assistance is appreciated!


1 ACCEPTED SOLUTION

Accepted Solutions

I believe I found a decent enough solution: equals(triggerOutputs()['body/PromotedState'],2)

I was checking a few tests and noticed that "IsCheckedOut" field was not there so I looked for another variable to compare finished published page vs drafts. 
I came across a post mentioned PromotedState:

Relloy_0-1691689752155.png

 

So now my trigger only fires on published pages which my intention for now. 
I appreciate your replies which honestly gave me a few hints on where I should look next. 



View solution in original post

7 REPLIES 7

Not sure about everything you are doing, but I know the Yes/No options are always tricky to deal with.

 

I can't tell what value you are using to update the Toggle field, but I would test "0" or int(0) and see if that changes anything.

 

I think using zero 0 is what will set a Yes/No field to No.

 

As for all of the HTTP request stuff, I don't know, but try updating the field with different types of the number zero 0 and see if that helps.

Ah I forgot to add that information more clearly, in my original post I was updating the Toggle field with a "0".

Relloy_0-1691603155594.png

 



I have attempted with a int(0) (as plain text and as a expression). It seems to produce a similar reaction, it gets stuck on the SavePage method with the status message "BadGateway". 

Hmm, I guess if Yes/No options on sharepoint are tricky I will try to use a "Number" Column instead and simply flip between 0 & 1 just like a Yes/No would. 

Any other further advice would be appreciated, if you require to see more into my flow let me know which part and I will try to provide you the context. 

 

Thanks

Did you double check the column name and make sure it is Toggle? 

 

There is an internal column name and a display/title name of a column. If you initially created the column with a different name and changed it, the you should try using the original name.

You could also try adding the headers that are shown in your example link. The Accept header really should only impact what data is returned, but the Content Type might make a difference.

 

wskinnermctc_0-1691605792045.png

 

The example used odata=verbose, but you don't have any metadata in your body so I put odata=nometadata

 

{
  "Accept": "application/json;odata=nometadata",
  "Content-Type": "application/json;odata=nometadata"
}

 

I'm not an expert at http requests, really just troubleshoot guessing.

Relloy
Regular Visitor

Regarding your two points, I have confirmed the internal name of the column is also "Toggle" and I have attempted to add the accept and content header. Unfortunately the flow reacted the same as before.

I might have found an alternative solution, rather than using HTTP requests, I can use "Update Item". 

Relloy_0-1691674095337.png

 

After a few tests it appears to be working well when creating a new post, after its posted the Yes/No column gets updated like expected.

I am now running into a problem with SharePoint's AutoSave Draft feature, if somebody idles a bit on making a new post it simply creates a new file with a generated name until its finally published.

Relloy_1-1691674512213.png

 


This is a problem because the trigger fires as this draft gets created. I looked for a way to disable this AutoSave Draft but I have not found anything so far. So funny enough it does update the Toggle column even if its a draft, but it posts with the draft version and then when finally published it does not trigger since the Toggle column is already updated.

I have tried adding 

@not(triggerOutputs()?['body/{IsCheckedOut}'])

to my trigger conditions but then it does not trigger on a regular Post as well. I will try a bit more troubleshooting but if you are able to see my mistake let me know.

I appreciate all the advice you have given, thanks!

I'm unsure about that trigger condition. I think it's on the right track, but it might need to be more clear about comparing values. 

I don't know what the outputs are supposed to be, but I know the trigger condition has to equal true.

 

Is there like a field "IsCheckedOut" = true in the body? 

 

You could try something like equals(triggerOutputs()?['body/{IsCheckedOut}'],true) 

or equals(triggerOutputs()?['body/{IsCheckedOut}']?['Value'],true)

 

Not exactly sure and you probably know better,

I believe I found a decent enough solution: equals(triggerOutputs()['body/PromotedState'],2)

I was checking a few tests and noticed that "IsCheckedOut" field was not there so I looked for another variable to compare finished published page vs drafts. 
I came across a post mentioned PromotedState:

Relloy_0-1691689752155.png

 

So now my trigger only fires on published pages which my intention for now. 
I appreciate your replies which honestly gave me a few hints on where I should look next. 



Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (882)