When developing a SharePoint Framework Extension to display a custom header and/or footer, the SharePoint Composite Header can be very redundant to the custom header.

The Composite Header (css classname is 'ms-compositeHeader'), is what SharePoint provide out of the box and includes the square site logo, site name and navigation.

When creating your own custom header that includes all of these things and possibly more, the existence of the Composite Header is redundant and can be confusing for users...(Ex: redundant navigation).

While CSS can be used to hide this, such a technique is not playing within the rules of only controlling the DOM elements created by the extension.

This request is to have a configurable property created that can hide the composite header to remove the redundancy when creating a custom header.

This could be a site property configured using PowerShell or a property defined in the SPFx Extension itself.

This would help ensure that rogue overriding of the CSS to hide the Composite Header does not occur and helps developers to stay within the rules requested by Microsoft when developing for the Modern Experience.

We live in a tenant where we have over 25 different companies. When it comes to customizing and supporting the tenant catalog is too broad, but the site collection catalog adds support nightmares with syncing and managing the apps and installs in each one. It would be great if the site collection admin could choose an additional Site Collection app catalog to pull from. This would allow for us to manage company specific apps in a Company site collection catalog much like the tenant catalog while still getting site specific catalog items from the site collection catalog. In this model, there would be three levels a site admin could get apps from, Tenant app catalog, local Site Collection App catalog and this new configurable remote site collection app catalog.

Currently we have business case where SharePoint App registration(SPO App ID/Secrets) are vastly used by users for their applications. I had discussion with MS Development support engineer and there is no way to track the owner of SPO app registration (SPO App ID/Secrets).

It would be helpful if during registration of SPO app id/secrets, the owner information also be asked, so that whenever SPO App registration expiry comes near by, customer can notify that your SPO app id expiration coming please renew app secrets so that business application keeps running.

Preferable solution would be online connector and also Powershell commands that can track the information of owner of app id/secrets. I do see we can get expiry date of SPO app registration but not able to get owner of same. Also getting this information thru loop of each individual site collection would be very difficult especially when the number of site collection goes beyond 10k/20k...

SPFX extensions give us ability to add our own commands and to show/hide them based on different conditions e.g. state of the selected documents/

These commands usually change the state of the document, but onListViewUpdated from BaseListViewCommandSet is not triggered automatically (which is fine) and there is no way to manually trigger onListViewUpdated.

Through some google searches I found that there is module itemInvalidator with method invalidateCurrentItemSet. But it is hidden from JS API users.

The onlu options we have now are:
1) reload whole page - unacceptable in most cases
2) make user to reselect the item - one of the worst UX possible

Please make invalidateCurrentItemSet method available!

Thank you.

Recent licensing changes for Power Automate has made the Request - When a HTTP Request is received trigger a Premium action. This essentially removes the ability to call a Power Automate Flow from a Site Script since every user making the call would now require premium licensing.

Whats worse, is any Flow that was previously configured to use this trigger from a site script can no longer be updated and saved. You are given an error message about inaccurate licensing and prevented from saving. So anyone who had been using it for Site design and site script automation can no longer make changes without paying more for the privilege to do so.

This is a huge reduction in capabilities just so Microsoft can squeeze more money from customers. I for one am highly disappointed and would suggest fixing this. Stop turning everything into premium connectors!!!!!