Schema reconciliation, keeping the form in sync with SharePoint
How the form re-derives schema-driven properties from the live SharePoint columns on every load, preserving author overrides.
When a SharePoint list changes, a column is added, renamed, retyped, or its choice list updated, every form bound to that list re-derives the affected properties automatically. This process is schema reconciliation, and it runs on every form load.
What gets reconciled
Schema-driven properties are read from the live SpField[] and applied
to the matching components on load. Author overrides (label, cssClass, conditional
rules, validation messages) are preserved, only the schema-derived defaults
are refreshed.
| Property | Description |
|---|---|
required | If the SP column is marked required, the field is required (unless the author explicitly set required: false for a different reason). |
options | Choice / MultiChoice option lists pull from the column's choice values. Author overrides via the field's options property win. |
lookupListId & displayColumn | Lookup fields refresh their target list and display column. |
RichText flag | Note columns may toggle between plain text and rich text. The field type may swap between Textarea and RichText accordingly. |
Field type swap | If the SP column type changes (e.g. Text → Choice), the component type swaps too, author config that no longer applies is dropped with a warning. |
What stays untouched
Author-defined properties always win:
label,description,placeholder, your copycssClass,style, your brandingvisibleIf,enableIf,requiredIf, your rulespattern,assertExpression,assertMessage, your validationonChange,onValidate, etc., your event handlers
When reconciliation matters
- A column is renamed in SP. The form continues to work, internal names are the binding key, not display names.
- A new column is added to SP. The form ignores it (it's not on the form).
- A column is removed from SP. The form skips that field with a console warning. The SP write would have failed; better to drop it silently.
- A choice list is updated in SP. The form picks up the new options on next load.
When it doesn't help
Schema reconciliation only runs on form load. If the underlying schema changes while a user is filling out the form, they finish on the old schema. For forms with very long sessions, consider periodic reload prompts.
Related
Related articles
- SharePoint column types, overview
Which SharePoint column type binds to which Forms365 component, how values are read and written, and the SP-specific quirks per type.