SPFx Customizers Coming soon
Field, form and app extensions
Which SharePoint Framework extensions are bound where: field customizers on site and list columns, form customizers on content types, application customizers and list command sets. Bind, change and detach them, pick a component from the installed extensions, or report across sites with orphaned components.
What it does
- Which column renders through this field customizer?
- Is a component bound that no app catalog has any more?
- Which content types use a custom New or Edit form?
How it runs
- Sign in, then choose. Manage one site, or Report across sites.
- Manage. Four tabs: fields, forms, application customizers, command sets.
- Change. Configuration like this has no recycle bin, so ShareMaster re-reads it first, refuses if it changed since you loaded it, saves a backup file before anything changes, asks you, then reads it back. Backups restore from the Backups button. Detaching one form keeps the other two exactly as they were.
How it works
Manage reads field customizers on site columns and list columns, New, Edit and Display form customizers on site and list content types, and the application customizers and list command sets on the site. The component picker is filled from the tenant and site collection app catalogs this sign-in can read, and marks a tenant component whose app is not added to this site. Binding a component id that is in no readable catalog asks you first. Report mode reads the sites you pick, lists bound ids that appear in no readable catalog as orphaned, and changes nothing.
A field binding sets the column's component and its JSON properties; detaching writes an empty component and empty properties. A site column change reaches the lists that use it only when you tick that box. A form binding always writes all six form settings of the content type (component and properties for each form), copied from a fresh read, so the forms you did not choose keep exactly what they had. A new application customizer is added at site collection scope, and a new command set at web scope for a list template or on one list.
Every bind, change, detach and restore re-reads the column, content type or action, stops if it changed since you loaded it, saves a backup file on this computer, asks you, writes and reads it back. A failed backup means nothing is sent, and a read-back that does not match is reported as a failure. More than ten bindings in one action asks you to type the count. Each change is written to the app log.
Application customizers and command sets are custom actions, so they are written through the same path as the Custom Actions tile and their backups are filed there: restore them from that tile's Backups. Field and form bindings are restored from this page. ShareMaster never installs, adds or removes an app.
What you get
An Excel workbook, named like SPFx customizers 2026-10-07 14-22.xlsx, kept in Report History whether or not you save it.
Summary sheet
Counts per kind and one row per site.
SPFx customizers sheet
One row per binding.
| Column | Example |
|---|---|
| Site | https://contoso.sharepoint.com/sites/hr |
| Kind | Field |
| Target | Status (Status) |
| Component id | 8928f1df-... |
Orphaned components sheet
Bound component ids that are in no catalog this sign-in can read.
Refused sheet
Sites or parts that could not be read, with the reason.
What you need
- Site owner (Full Control) on the site.
- Read on the app catalog to list installed extensions. Without it, a component id can still be typed.
What it will not do
- A component that is in the catalog but not added to the site will not render until the app is added. ShareMaster does not install apps.
- A site column change is pushed to the lists that use it only when you tick that box.
- Properties must be valid JSON.