Web Property Bag and NoScript Sites

%3CLINGO-SUB%20id%3D%22lingo-sub-55971%22%20slang%3D%22en-US%22%3EWeb%20Property%20Bag%20and%20NoScript%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55971%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.techmikael.com%2F2017%2F02%2Fgaps-and-differences-between-group-365.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.techmikael.com%2F2017%2F02%2Fgaps-and-differences-between-group-365.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22You%20cannot%20programmatically%20update%20the%20site%20property%20bag%20on%20a%20modern%20site%2C%20but%20in%20many%20cases%20you%20can%20work%20around%20this.%20This%20has%20traditionally%20been%20used%20to%20store%20site%20meta%20data.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDigging%20into%20the%20modern%20site%20experience%20it%20seems%20the%20previously%20available%20ability%20to%20manage%20custom%20scripting%20for%20self%20service%20sites%20has%20been%20removed%20entirely.%26nbsp%3B%20This%20has%20been%20the%20most%20common%20way%20to%20add%20metadata%20to%20the%20SPSite%20object%20for%20search%20purposes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20on%20the%20roadmap%20to%20fix%3F%26nbsp%3B%20Has%20anyone%20found%20a%20way%20around%20the%20NoScript%20limitation%20on%20property%20bag%20editing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-55971%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAPIs%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPnP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253443%22%20slang%3D%22en-US%22%3ERe%3A%20Web%20Property%20Bag%20and%20NoScript%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253443%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20turn%20off%20NoScript%2C%20update%20the%20propertybag%2C%20and%20turn%20it%20back%20on!%20Here%20is%20now%20PnP%20does%20it%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2FPnP-Sites-Core%2Fblob%2Fmaster%2FCore%2FOfficeDevPnP.Core%2FExtensions%2FTenantExtensions.cs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2FPnP-Sites-Core%2Fblob%2Fmaster%2FCore%2FOfficeDevPnP.Core%2FExtensions%2FTenantExtensions.cs%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(Search%20for%26nbsp%3B%3CSPAN%20class%3D%22pl-smi%22%3EDenyAddAndCustomizePages)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56169%22%20slang%3D%22en-US%22%3ERe%3A%20Web%20Property%20Bag%20and%20NoScript%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56169%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20could%20use%20sp%20editor%20extention%20in%20chrome%20for%20the%20time%20being%20but%20it%20is%20not%20a%20solution%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E
New Contributor

http://www.techmikael.com/2017/02/gaps-and-differences-between-group-365.html

 

"You cannot programmatically update the site property bag on a modern site, but in many cases you can work around this. This has traditionally been used to store site meta data."

 

Digging into the modern site experience it seems the previously available ability to manage custom scripting for self service sites has been removed entirely.  This has been the most common way to add metadata to the SPSite object for search purposes.

 

Is this on the roadmap to fix?  Has anyone found a way around the NoScript limitation on property bag editing?

2 Replies

You could use sp editor extention in chrome for the time being but it is not a solution :)


You can turn off NoScript, update the propertybag, and turn it back on! Here is now PnP does it: https://github.com/SharePoint/PnP-Sites-Core/blob/master/Core/OfficeDevPnP.Core/Extensions/TenantExt...

 

(Search for DenyAddAndCustomizePages)