-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support moving cross-site collection with spo file move
#6153
Comments
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 5, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 11, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 15, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 15, 2024
martinlingstuyl
pushed a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 20, 2024
Fixed in #6271 |
martinlingstuyl
pushed a commit
that referenced
this issue
Sep 20, 2024
milanholemans
added a commit
that referenced
this issue
Sep 21, 2024
MathijsVerbeeck
pushed a commit
that referenced
this issue
Sep 24, 2024
Adam-it
pushed a commit
that referenced
this issue
Sep 27, 2024
ktskumar
pushed a commit
to ktskumar/cli-microsoft365
that referenced
this issue
Oct 8, 2024
ktskumar
pushed a commit
to ktskumar/cli-microsoft365
that referenced
this issue
Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In v7, we moved the command spo file move to a new endpoint. While this works great and fast within the same site collection, this endpoint doesn't support moving "large" files to other site collections. When doing so, you're getting the error below:
Even for relatively small files (50MB in the example), the command fails. This is not really ideal in my opinion. Let's look for alternatives when moving files to another site collection. If we are moving to the same site collection, I would stick with the current API request since it's super fast and flexible. When moving cross-site collection, we'll probably have to use a copy job API to make it work.
In this case, it's also important to:
nameConflictBehavior
:fail
,replace
,rename
Let's look for the best approach to fix this.
Tagging this with V9 since this might possibly be a breaking change.
To do:
The text was updated successfully, but these errors were encountered: