Skip to content
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

FilePicker: unable to browse through organization assets library when located on root site #1784

Open
BollietMZK opened this issue Feb 29, 2024 · 3 comments

Comments

@BollietMZK
Copy link

BollietMZK commented Feb 29, 2024

Category

[ ] Enhancement

[X] Bug

[ ] Question

Version

Please specify what version of the library you are using: [3.17.0]

Expected / Desired Behavior / Question

I have an organization assets library on the root site of my tenant.
I use the FilePicker component to browse inside this specific library via the relevant option.

Observed Behavior

When I select my organization assets library on root site, I have an infinite loading:
image
(sorry for the french texts).

The error is:
image

I think this is because of this following request to get the items of my library:
https://***.sharepoint.com/sites/my-site/_api/SP.List.GetListDataAsStream?listFullUrl=%27https://***.sharepoint.com//%27&RootFolder=/Org%20Assets

We can see a double slash after .sharepoint.com: //

Steps to Reproduce

  1. In PowerShell, specify an organization assets library located on the root site of the tenant
  2. Add a FilePicker component to your webpart
  3. Browse inside the option "Your organization" (as I am french, I don't know the correct translated text for the option).
@ghost
Copy link

ghost commented Feb 29, 2024

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@michaelmaillot
Copy link
Collaborator

Hi @BollietMZK,

Thanks for raising this issue, I confirm I can repro even in latest version (3.20.0).

Would you like to try to fix this?

@albegut
Copy link

albegut commented Feb 20, 2025

Hi @michaelmaillot I've just create the PR #1954 to solve this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants