get-O365-drive-id does not give detail as to which share is which #1349
-
when I run I expect it to show some indication of which drive-id relates to which shared library eg
built from source on debian bullseye today.
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
The output does .. so I am unsure what the issue is here ... also your totally 'redacted' output basically tells me nothing of your issue. For example: output when site name cannot be found:
searching for 'testteamsite':
Notes:
You should be able to tell which drive_id is associated with what sitename & URL from the application output without issue. If you have named all your SharePoint sites the same name - that is something I cannot assist with ......... |
Beta Was this translation helpful? Give feedback.
-
Closing issue, not a bug or issue |
Beta Was this translation helpful? Give feedback.
-
We have 2 Shared Libraries, and 7 "Document Libraries" within one of the shared libraries. The output I pasted above is exactly as is except I redacted the drive ids. the output from
Each of the drive id's output by the command do relate to the shared libraries, and seem to be in the same order as they appear in the screenshot. they just don't show any indicator as to the name. |
Beta Was this translation helpful? Give feedback.
-
There lies your issue. The It is not for getting / listing the document / folders under that Shared Library - however I do find it interesting that it is listing those when you use that configuration option ... as I am unable to replicate that sort of behavior. This being said, the client option is functioning as expected and as documented. |
Beta Was this translation helpful? Give feedback.
-
@jasonblewis In this situation - when there multiple document libraries, it is difficult to tell what is what. As such, this is not a bug, but a feature enhancement (as the existing works, as advertised). Please can you test the following PR:
To run the PR, you need to run the client from the PR build directory:
When running the PR, your version should be: Example when running the PR:
Please can you test and validate this enhancement. |
Beta Was this translation helpful? Give feedback.
@jasonblewis
In looking at this further I have been able to create 'document libraries' within a SharePoint Library to replicate your use case / environment.
In this situation - when there multiple document libraries, it is difficult to tell what is what. As such, this is not a bug, but a feature enhancement (as the existing works, as advertised).
Please can you test the following PR:
To run the PR, you need to run the client from the PR build directory:
When running the PR, your version should be:
onedr…