Forum Discussion
SPFx Tenant Properties Preview now available for First Release tenants
Hi All,
Tenant properties allow tenant administrators to add properties in the app catalog that can be read by various SharePoint Framework components. The tenant properties are managed by tenant administrators using the https://technet.microsoft.com/en-us/library/fp161372.aspx which is a PowerShell module to manage your SharePoint Online subscription in the Office 365.
Tenant Properties is currently in preview and is available to First Release tenants.
Here is the documentation on how to use the SharePoint Online Management Shell to manage properties and use the REST API to read those properties: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/tenant-properties
We would love to hear your feedback! Do post your comments/feedback/suggestions below!
11 Replies
- Terry HaganIron ContributorHi, the link to docs comes up with a 404.
- Chakkaradeep (Chaks) Chinnakonda ChandranFormer Employee
Thanks! Not sure what changed but it works now.
- kath pattersonIron Contributor
great to see the ever useful old 'property bag' resurface.
be good to see PnP JS Core encapsulate the GET request to make this neater and obviate uneeded code lines. hopefully in next release perhaps?
- Gautam ShethBrass Contributor
What will happen if the key already exists and we run the Set-SPOStorageEntity again ? Will it be overwritten or throw error ?
Would be amazing if we could also have something like Update-SPOStorageEntity and Delete-SPOStorageEntity or Remove-SPOStorageEntity as well.
Also, is there any character limit to this ?
- Chakkaradeep (Chaks) Chinnakonda ChandranFormer EmployeeIf you do set on an existing key, it will update that key if it exists with the new value.
Yes, we have Remove-SPOStorageEntity to remove keys.
I am not aware of character limitations, but can you test if you have those special characters failing?
- Oliver ZeiserBrass ContributorThe values for comments and description are interchanged at the moment. I have created an issue on github already, just wanted to warn the people reading here as well...
- Chakkaradeep (Chaks) Chinnakonda ChandranFormer EmployeeThanks! Yes, this is a known issue and will be fixed soon!