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:
- Be able to specify a new name
- Be able to use the same
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:
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,renameLet's look for the best approach to fix this.
Tagging this with V9 since this might possibly be a breaking change.
To do: