pnp / pnp/sp-dev-fx-controls-react

🔧 Enhancement Request: Persistent Multi-Folder File Selection within a Single Site in PnP File Picker

Open
#2,013 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
433
Forks
418
Avg merge
5d 6m
Merged PRs (30d)
19

Description

Target environment

Browser App (Hosted external to Microsoft 365 platform)

Additional environment details

We are using a custom Angular application hosted externally (outside Microsoft 365). The integration uses:

  • @pnp/picker-api for file picking
  • @microsoft/microsoft-graph-client for Graph API access
  • Auth is handled using getTokenWithScopes for scopes like Sites.Read.All and Files.Read.All.

The picker is embedded within our component using an <iframe> with the Popup() and LamdaAuthenticate() strategy.

Our desired behavior is to allow persistent multi-folder file selection within a single SharePoint site session, which would greatly improve usability.

Enhancement Idea

Dear PnP Team,

First, thank you for your outstanding work on the PnP File Picker and the broader Microsoft 365 development tools. Your efforts have greatly simplified our integration processes and improved the overall development experience.

📌 Context

We have already integrated the PnP File Picker into our Angular-based document management platform. It allows users to select and submit files from SharePoint document libraries.

Problem Statement
  • When users navigate to a different folder within the same site to pick additional files,
    previously selected files are lost.
  • This disrupts the file selection flow and forces users to reselect files from scratch.
  • The experience becomes frustrating, especially when users need to gather multiple files stored across different folders under the same site.
What We’re Hoping For

We would be truly grateful if the picker could support:

➡️ Persistent file selections across folder navigation within the same SharePoint site.

If this enhancement were available, it would significantly improve our file selection workflow and reduce repetitive actions.

🌍 Why It Matters
  • Allows users to build a complete file selection across folders without losing previous picks.
  • Enhances user efficiency and reduces frustration in multi-folder workflows.
  • Makes the picker more flexible and enterprise-ready.
  • Reduces the need for custom workarounds or external state management logic.

Thank you for considering this enhancement.
We would truly appreciate it if you could let us know if this is planned and when we might expect it, as this feature is needed at the earliest on our end. 🙏

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the PnP File Picker integration in the embedded iframe, including the Popup() and LamdaAuthenticate() strategies, and trace how selections change during folder navigation. Done means files selected from multiple folders within one SharePoint site remain selected instead of being lost.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.