Closed pri-kise closed 2 years ago
Hi,
definitely a good idea. I may implement this if I can find time for it.
Thank you.
Hi,
with v0.3.0 you can now just use the SharePoint document library url instead of the drive id, like so:
This works for document libs in "normal" sites, subsites and in the root sharepoint site.
Just make sure, that you use the full URL, including the name of the library, but not any further paths like .../Shared%20Documents/Forms/AllItems.aspx
. I missed that hint in the README, will fix that later.
Thanks for implementing this cool enhancement.
Hi. I have finally enough access to try again. But I got "itemNotFound".
Does this have to do with this ticket and how I am giving it this
"driveId: 'https://$(sharepoint_host)/$(sharepoint_site)/$(sharepoint_dir)/$(sharepoint_remoteDir)'"
which is in fact a url (because I do not have access to get the ids)?
UPDATE: I've split it to 'driveId' and 'targetFolder' but still nothing.
I am using the "az-pipelines-2-sharepoint@0"/0.3.4.
I will try using the code above meanwhile, to check if it bypasses security and actually returns some ids...
Sorry, and thanks!
Hi,
I had some problems figuring out the DriveID, since we are using drives of subsites. What do you think about an additional task that accepts the
Url
of the Object Library and sets the DriveId as a pipeline variable?Here a small draft for getting the drive id by using powershell. I'm sure this can be achived by using javascript, too.
Example to set a pipeline variable: https://stackoverflow.com/q/70425335/6068675