Repository navigation
Error 501: when uploading a new file #894
Description
Describe the bug
I'm trying to replicate the HTTP example with the Python SDK as here:
async with aiofiles.open(src_file_path, 'rb') as file:
file_content = await file.read()
dest_folder_name = "FolderA"
src_file_name = "FileB.txt"
dest_file_path = f"{dest_folder_name}/{src_file_name}"
drive_item_id = f"/root:/{dest_file_path}:"
uploaded_file = await self.client.drives.by_drive_id(drive_id).items.by_drive_item_id(drive_item_id).content.put(file_content)
But I get a 501 error with message
Cannot upload content to an item representing a folder.
Expected behavior
The file should be uploaded, but I believe there is a problem in the way the drive_item_id is built in the by_drive_item_id method.
How to reproduce
dest_folder_name = "FolderA"
src_file_name = "FileB.txt"
dest_file_path = f"{dest_folder_name}/{src_file_name}"
drive_item_id = f"/root:/{dest_file_path}:"
# drive_item_id example: '/root:/FolderA/FileB.txt:'
uploaded_file = await self.client.drives.by_drive_id(drive_id).items.by_drive_item_id(drive_item_id).content.put(file_content)
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```msgraph.generated.models.o_data_errors.o_data_error.ODataError:
APIError
Code: 501
message: None
error: MainError(additional_data={}, code='notSupported', details=None, inner_error=InnerError(..., message='Cannot upload content to an item representing a folder.', target=None)
</details>
### Configuration
_No response_
### Other information
_No response_
Activity
shemogumbe commentedon Sep 12, 2024
Hello Luca (@LuchiLucs) thanks for using the SDK and for raising this,
A few pointers in your upload code,
-drive-item - shis should be a
DriveItemUploadablePropertiesobject atfrom msgraph.generated.models.drive_item_uploadable_properties import DriveItemUploadablePropertiesThen upload content using PUT,
Optionally use an upload session to upload with a post:
microsoft-github-policy-service commentedon Sep 16, 2024
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.