SPFx Key/Value Pair Properties that support Read/Write
Provide a SharePoint Framework mechanism/API that allows for Site or Site Collection Read/Write of Key/Value pair properties for use in SPFx related configuration and customizations. Similar to how the property bag was used in classic.
One use case is for storing configurable properties or even user personalization configurations written and read by an SPFx solution.
This is one of many uses cases that would make this feature valuable, so in addition to your vote, please feel free to comment with additional ways in which this feature could provide additional value.
David Warner
shared this idea
6 comments
-
Martin Laplante
commented
The easiest solution is to not have the blanket restriction on writing to the property bag with NoScript. Restrict it so it's not a free-for-all, but allow some apps to modify their own.
-
Patrick
commented
With modern SPO site architecture, it's common for solutions for managing Projects/Programs/Proposals to span [n number of site collections] all bound to a given Hub Site.
However, there's a need to maintain metadata for each "Project" bucket alongside the site itself and aggregate that metadata across site collections for reporting needs. The "no script" nature of modern team sites, makes the manipulation of the property bag itself not a realistic option.
This is a HUGE need for future solution development on the platform.
-
Pontus
commented
A Graph API call we can use in Flow for this would be really useful. There's no good way to work with the site objects today.
-
Tom Daly
commented
i'd like to be able to create an application customizer and be able to configure it per activation / site collection. Key/Value pairs could help.
-
Leo Siddle
commented
The classic property bag APIs also exist for folders - and a common use-case is to store list/library related config values in the root folder for the list or library.
If there was going to be a new equivalent API to the classic property bag APIs, it would be great if this was also included.
Thanks
-
Alex Terentiev
commented
More Use Cases: storing custom provisioning properties like IsConfigured, IsFinalized, etc.
A bit more background: we need that functionality for NoScript sites where editing of site's Property Bag is disabled
