When trying to add SPFX webpart to classic publishing page, sp.runtime.js is trying to load twice which is causing a conflict and resulting in the page to breaking, I have tried a few workaround but hasn't solved my issue.

Within the SPFX 'extension' framework, there's no way to specify an icon for a ribbon button - list view extender.

This blog post mentions it - but no resolution ;
https://github.com/SharePoint/sp-dev-docs/issues/642

Ideally, there would be a property for ; officeFabricIconFontName

I am a fan of Site Designs; however, I would like to be able to set Default Column Values on lists and folders.

You could complete this action using the UI or the Set-PnPDefaultColumnValues PowerShell complete. Sadly, this is not in acceptable to the average “business user” and required administrator input.

Please add a verb called setDefaultColumnValues to SharePoint Site Scripts?

As described in this doc: https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread
When granted All Site Full Control permission, the application would be able to access all sites in my organization. But can we grant permissions to specific sites? In other words, can we restrict the sites the application can access? If we can, how to do this?

There is a bug in the Online Workbench that you are not able to test theming on your web parts when the following two themes will be used:
* Dark Yellow
* Dark Blue

As documented in the Issue on GitHub https://github.com/SharePoint/sp-dev-docs/issues/1064

This would be really beneficial for testing web parts and how they look like when different themes will be used.

I created a column that is a linked to item lookup field to a different list and pops up a dialog box to that item when clicked. I only get @currentField.lookupId or @currentField.lookupValue for the JSON formatting - and would like to have the "@currentField.lookupUrl" so that I can display a button or different link text - yet have it act like the "linked to item" link which inherits whether or not it opens in a dialog box from the "advanced settings" or the list.

JSON formatting is nice and dandy, I would like some more operators though.

Specifically .parse() to interpret the contents of @currentField as a JSON object, and split() to interpret is an an array, split by whichever operator is provided.

Web description and user id are both strangely missing from the page context. It would be great of they were available.

Add the ability to hide column when adding it to the content type - on the addSiteColumn JSON script.

Environment: SPO

There is a new option to allow the team site owners to receive the access requests email, but there is no Rest API/CSOM to support this, Please have add this into CSOM API, Thank you.

Currently, it's not possible to add a web part to a newly created modern site (communication or team site):

• Adding a web part is not supported in site designs.


• Adding a web part with PnP (CSOM: ClientSidePage.AddControl; PowerShell: Add-PnPClientSideWebPart) removes all default web parts.

It would be good to support either scenario or, even better, both.

When using the SharePoint Framework, you should be able to request webApiPermissions via the resource client Id OR the resource name.

We have a multi-tenant application that's deployed to a couple dozen tenancies that we would like to rename. However, since permissions are requested by name, any attempt to rename the application may be met with our users having to go through the install process again. Being able to instead request access via the clientId would allow us to safely rename without having to worry about our users losing access.

If a Task list (template 171) has fewer than 5000 items, the performance of the RenderListDataAsStream endpoint is inappropriate (try with 4999 items). If the list has 5000 or more elements the performance becomes excellent. I know that the tasks lists are not compatible with Modern UI, but this should not affect the RenderListDataAsStream endpoint as well.

Provide CSOM API for Enabling/Disabling the option "Allow items in this list to be edited using Quick Edit and the Details Pane".

After migration of SharePoint Previous versions to SharePoint online, there are instances where the quick edit or edits from details pane needs to be disabled, for lists across thousands of site collections. This is very challenging task if has to be done manually for huge scale of site collections.

When using @now to format views/columns using JSON the date is taken as the US style (mm/dd/yyyy) regardless of the regional settings of the tenant. It would be useful if it either uses the date format of the tenant, or allows the user to specify the date format. For more details of the problem see here: https://social.technet.microsoft.com/Forums/msonline/en-US/21712788-fafa-4898-9cee-897d1b3afb88/modern-list-view-formatting-with-uk-dates?forum=onlineservicessharepoint

Please add functionality to create roledefinitions, create custom groups and assign roledefinitions to groups.

When using the AadHttpClient within a SPFx WebPart, a popup appears that is currently necessary to facilitate authenticate to Azure AD (part of ADAL JS). While this is understandable if the user needs to supply additional authentication components, if the user has the necessary rights to the Azure secured API, no popup should be presented.

Scenarios where this behavior is not acceptable:
- Pages with multiple third party data sources (user is bombarded with popups)
- High traffic landing pages (like corporate home pages) where look & feel are crucial

Documentation on behavior:
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aad-tutorial

GitHub Issue relating to this:
https://github.com/SharePoint/sp-dev-docs/issues/1471

Much like the classic SSOM model of extending OOB web parts, provide a way (or open source them ;-)) the SPFX web parts to allow Devs to build upon what you have already built.

Its a bit old school, but has value in providing Devs a way to extend existing web parts leverage them and tweak them according to specific requirements. Perhaps with a change caveat that if you change it does not update our custom ones based upon it.