cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
VDG
Helper I
Helper I

Copy file across different SharePoints - keep version history

Hello guys!

I am currently working on an automation which copies a specific file from SharePoint A to SharePoint B once a week.

My goal is to not only copy the file and it's contents but also to keep all of it's metadata and versioning history.

 

The problem is well known in the community. When copying the file via Copy file from SharePoint A to B, all of my metadata and versioning history gets lost for the file in SharePoint B.

 

I looked into dozens of community posts regarding this topic, including different approaches with HTTP, Create, Copy, Move and Update strategies but none of them worked the way I wanted.

It is a basic Copy from A to B.


Many thanks!

 

Best regards.

 


Screenshot 2024-03-22 135536.png

 

 

 

 

 

10 REPLIES 10

Hi @VDG ,

Quick note on the copy action, when you are using it, it recreate a new file (therefore V1 in terme of versionning). Only the move ensure to keep the history of your file.

Regarding your metadata, are you using SharePoint columns to store them or you are mentionning the file metadata (within properties).

SharePoint columns : 

Tristan_D_0-1711115126683.png

Properties :

Tristan_D_1-1711115511021.png


T

Andrew_J
Memorable Member
Memorable Member

@Tristan_D 

 

Sorry to but in, however are you saying that it would be a good idea to store the versioning data of a file in a SP List along with that file in the attachment even though you move or copy it between the Libraries and possible loos all of that.  I am only asking for my learning.

 

Regards,

 

Andrew

Hi @Tristan_D!

Thank you very much for your quick reply.

 

I already tried to use the Move file functionality. The issue is that the file in SharePoint A is read only, so moving the file will not work. Copying, as you said, creates a new file for itself with the disadvantage if losing metadata.

 

I use the file metadata within properties.

 

Best regards. 

 

Hi @Andrew_J ,

Not really, the versionning is already present as a native functionnality in SharePoint and can be managed in the versionning settings :

Tristan_D_0-1711123150090.png

I was rather mentionning that when you copy a file, it creates a brand new file with a new identificator.

There is an idea which have been posted few years back asking to implement this function though it hasn't been done :

https://ideas.powerautomate.com/d365community/idea/fb43ed07-ddbc-4ee3-a34a-022992a9c96b 

Another thread answering how to retain the version when copied has been answered here :
https://powerusers.microsoft.com/t5/Building-Flows/Copy-file-to-location-maintaining-version-history...

though it needs to be done via an HTTP request 😉 and storing the verion detail in a specific column.

Let me know if that helps you.

T

No worries @VDG !

Have you got a possibility to move your metadata in columns ? if you are using a Office365 suite, you can access thoses "properties" directly in the app. 

To do so, you need to allow the management of content types in the advanced settings option of your library :

Tristan_D_1-1711126399698.png


When that is done, it activate the SharePoint Panel (Document Information Panel) within your applications :

Tristan_D_2-1711126468129.png


From there you can dynamically update the columns.

Let me know if that could be one of your option for you ?

T

Hi Tristan,

thanks again for your reply.

 

I am kind of new to the whole SharePoint automation topic, so I did not get you quiet right. What do you mean with "Have you got a possibility to move your metadata in columns"?

 

For information: I have an Excel-sheet stored in a Document library.

 

Would it be a plausible solution to convert this Excel-sheet to a SharePoint List and then add a column which has the relevant version history information? 

I checked the links you provided in your reply to @Andrew_J and I guess they used SharePoint lists too.

 

Best regards.

 

Hi @VDG ,

Two points  : 

First, when you start to consider using SharePoint, the best practice is to "move" the metadata into columns, it allows you to view them directly and to create associated views.

You would obtain something like that : 

Tristan_D_0-1711470640355.png

 

Now, the second point is regarding your excel.
If you are only using excel to store rows of data and not perform complex operations like pivot table, I would urge you to pass those data into a SharePoint list, it will allow you not only to enable the versionning of your data but also to allow a real collaborative work.

Example:

Let's take an excel as following (Making sure that the data is formated as a table) : 

Tristan_D_1-1711470959576.png

 

this one is saved in a Sharepoint library.

You could create a new list based on this file by going back on the home page and create a new list from an excel :

Tristan_D_2-1711471192734.pngTristan_D_3-1711471377137.png


Then, you can either pick directly the file or look for it in your arborescence :

Tristan_D_4-1711471443798.png

it then ask you to associate the columns :

Tristan_D_5-1711474049070.png


When you are done, it will create the list : 

Tristan_D_6-1711474212780.png

 

And as you can see below , each item got a versionning already enabled:

Tristan_D_7-1711474261484.png
Tristan_D_8-1711474277973.png

Is it clearer for you ?

T



Hi @Tristan_D!

I really appreciate your afford to answer my questions in detail. 

 

I followed your steps and got my first SharePoint List.

The problem now is that the items have their own version history which is great but the history from my Excel Sheet is not applied to them. The version history starts from sratch again.

 

What about a Pyhton script which downloads and uploads the Excel Sheet to a different location. What do you think @Tristan_D?

 

I really can not understand why there is no plausible approach for a copy function like that.

 

Best regards.

 

No worries @VDG .

Sadly, your Excel versionning (history) is linked to a file and the rows inside aren't unique therefore, it logs an history of your modifications on a file level not a row level.

 

In terme of change, I would suggest you to lock this file in read only in order to keep the history and to move the production to this SharePoint list.

I am not at all proficient in Python so can't telll you what is possible or not in the matter.

Regarding the copy function, keep in mind what I explained above, in my opinion, you are trying to obtain an history of a single excel file and "split" it by row for each list item... I would really challenge this type of requirement at the office ^^.

Hope it helps.

T

Hi @Tristan_D

thank you very much for your help.

I think, I will follow your approach of using SharePoint Lists, even if I lose my version history. Cause it is a better solution for future work to start with a new but consistant version history.

 

Best regards. 

 

Best regards.

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 (378)