cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jlebbs_qqcw
Frequent Visitor

Send an HTTP Request - restoreversion Failing

I have a flow where I am trying to restore the version of a List Item if an approval is rejected. I'm following the documentation here, but I keep getting error 404 "Cannot find resource for the request restoreVersion.". I'm currently hard-coding the item # and the version ID # for testing, just trying to get this to work.

 

Here's the formatting I have: 

jlebbs_qqcw_0-1671083585192.png

 

Any help or suggestions figuring out how to solve this would be greatly appreciated!

1 ACCEPTED SOLUTION

Accepted Solutions
Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @jlebbs_qqcw,

 

That is the v2 version of the API, not the original API. The format for the URI is slightly different.

 

You also need to specify the site id, which is different in this endpoint, it is not a guid. And as far as I am aware you can also use the versionlabel instead of the versionid. Looking at the 72192 versionid I guess you are trying to restore version 141.0 (major versions increment by 512)

 

Try something like below:

 

 

_api/v2.0/sites/<siteid>/lists/<listid>/items/181/versions/141.0/restoreVersion

 

 

 

The siteid would be something like (which you can find in the Graph API)

 

 

contoso.sharepoint.com,<guid>,<guid>

 

 

Below is an example in my dev environment (with a different site id, item id and version label)

 

restoreversion.png

 

As you can see version 2.0 is restored as the new major version 4.0.

restoreversion_exampletest.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


View solution in original post

10 REPLIES 10
Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @jlebbs_qqcw,

 

That is the v2 version of the API, not the original API. The format for the URI is slightly different.

 

You also need to specify the site id, which is different in this endpoint, it is not a guid. And as far as I am aware you can also use the versionlabel instead of the versionid. Looking at the 72192 versionid I guess you are trying to restore version 141.0 (major versions increment by 512)

 

Try something like below:

 

 

_api/v2.0/sites/<siteid>/lists/<listid>/items/181/versions/141.0/restoreVersion

 

 

 

The siteid would be something like (which you can find in the Graph API)

 

 

contoso.sharepoint.com,<guid>,<guid>

 

 

Below is an example in my dev environment (with a different site id, item id and version label)

 

restoreversion.png

 

As you can see version 2.0 is restored as the new major version 4.0.

restoreversion_exampletest.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Brilliant, that worked, thank you!

Ok, now I created another problem for myself that this triggers my overall workflow again, since my trigger is "when an item is modified". Thoughts on how I can build an exclusion to avoid re-triggering the overall workflow?

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @jlebbs_qqcw,

 

Out of interest, why are you using this specific trigger?

 

Unfortunately, the restoreversion method does not have any additional properties.

 

As a workaround, you might be able to check who has changed it recently. If you have a service account restoring this version you can check if the Editor is not equal to that account in a condition or a trigger condition.



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


We're using this trigger to start an approval review process when data is changed on this list.

 

Good suggestion on the service account, although I don't think I'm currently configured that way. I do have a service account, but I'll have to configure that for testing.

Hi @Expiscornovus, thanks for the service account idea. I think I've figured out how to avoid making this recursive by specifically running the restoreversion as the service account, which logs the Item version history as that account rather than the end user.

 

Next thing to test and I think this will be it: filtering the trigger to NOT start the flow when the service account is the account making the change. I saw you replied on this thread about using a specific status to filter the trigger. Can the same logic be used to check the modified by email address? If so, could you point me in the right direction for that syntax?

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @jlebbs_qqcw,


Try something like below:

Replace my dummy email address by the one of your service account

@not(equals(triggerOutputs()?['body/Editor/Email'], 'john@contoso.onmicrosoft.com'))

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


That did it and avoided generating additional flows. Thank you so so much for your help!!!

Hi,


I know this is an older post, but it seems like the most relevant one I can find.  I am attempting to retore a version of a list items.  I can manually restore the item in SharePoint.  In flow I get a 400 

"Unexpected response from the service"  below is the Send an HTTP request I am using.
Any thoughts?
Thanks in advance.
ACCAgain_0-1695520587166.png

 

 

Hi,

 

I got this to work after a good night of sleep.  I was originally thinking about this as an item, but it really is a file in a document library.  Here is the working step that worked for me.

 

 

"Outputs" in my case is a Compose statement correctly formatting the Library Name and Folder Name 

 

replace('DocumentLibraryName/FolderName',' ','%20')
 

 

ACCAgain_0-1695578153380.png

 

I don't mean to drone or state the obvious just wanted to leave info of others who are interested.  

The case was what to do if I don't want to keep a change to file (metadata) in a document library. In my opinion I don't want to revert specific changes but just everything, back to the previous version.  Below is the more generalized solution.  

 

On change get the changed file properties  -  via Get file properties 

ACCAgain_4-1695581109479.png

Once I test the changes and decided to revert, in my case I want to revert to the previous version.

With the Get file properties I have all that I need 

 - Folder Path

 -File Name

 -Version Number

 

Now I need to transform these with Compose statement and the Send an HTTP request to SharePoint 

 

1-Compose Folder Path  

replace(outputs('Get_file_properties_2')?['body/{Path}'],' ','%20')

 

2-Compose  File Name

replace(outputs('Get_file_properties_2')?['body/{FilenameWithExtension}'],' ','%20')

 

3-Compose Version Number 

ConCat(String(add(int(outputs('Get_file_properties_2')?['body/{VersionNumber}']),-1)),'.0')

 

ACCAgain_5-1695581413573.png

Maybe I should not be doing this because of some possible unknown ramification, so use this at your own risk.

l would be interested in anyone's opinion.

Thanks

 

 

 

 

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 (3,545)