Hello,
I am moving files from one library to another one. I am getting save conflict error for some files and when I re-run the flow some of the errors get cleared. No-one has the files open. I use a get items(100 files/run) action to get the files and under apply to each I use the move files action to move them to a library.
Any idea why, is it because of the large number of files ?
Thanks,
Did you ever find a solution to this? Facing the exact same issue. Trying to move a file between sites and getting the same Save Conflict error. This file hasn't been update in two years, no one has it open but it does have almost 900 versions. I'm curious if the version history is the issue but can't find anything about limiting the number of versions that come over.
Hi @v-yamao-msft ,
I am facing the same issue as well. My flow is scheduled flow ,set up for moving files from 1 site to another. I have tried selecting the View with less columns, and 'Replace' action for files existing with same name. In fact , all the 3 options.
Yet, every time the flow is run, it ends up in Save Conflict error. I thought it might be due to moving multiple columns in one go, and set the row limit as '1', but it is still failing.
Here are some screenshots from Flow and the error message.
Thanks for help!
Best Regards,
I$H1Ta
Hi @ck25415 ,
Could you share a screen shot of your flow?
Have you selected Replace for field “If another file is already there”?
Do you have more than 100 files to be moved?
I have made a flow likes below, however, the conflict error doesn’t occur on my side.
Could you check the version history of the file to see if the file that got the conflict error has multiple version histories?
Sometimes, the save conflict error indicates the item was changed since the item was initially loaded and the update attempt was made, so you may need to resubmit the flow run to make it succeed.
Best regards,
Mabel
12 is the maximum number of lookup columns you can collect using an action or trigger in Flow. The threshold limit is hard set and can't be changed and it exists to maintain the performance of SharePoint.
So, to get around this threshold limit select or create a list view with no more than 12 total columns. Then choose that view from the Limit Columns by View option of the action.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
WarrenBelz
146,524
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,906
Most Valuable Professional