-
Notifications
You must be signed in to change notification settings - Fork 326
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 folder move
#6154
Comments
Fixed in #6271 |
Seems like I accidentally linked 2 different issues to the same PR. This issue is still active. Sorry for that 😊 |
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 26, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 26, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 26, 2024
milanholemans
added a commit
to milanholemans/cli-microsoft365
that referenced
this issue
Sep 28, 2024
tmaestrini
pushed a commit
to tmaestrini/cli-microsoft365
that referenced
this issue
Oct 22, 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 folder move to a new endpoint. While this works great and fast within the same site collection, this endpoint doesn't support moving "large" folders to other site collections. When doing so, you're getting the error below:
Even for relatively small folders (50MB in the example), the command fails. This is not really ideal in my opinion. Let's look for alternatives when moving folders 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
,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: