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.
Every SharePoint Forms365 field maps to exactly one SharePoint column type. The
mapping isn't always 1:1, some SP column types accept more than one component
(e.g. Note binds to either Textarea or RichText depending on the
RichText flag), and some components write to a column type that doesn't
obviously match their name (Email and Phone both bind to plain Text).
The mapping at a glance
| Property | Description |
|---|---|
Text | Single-line text. Binds to Text, Email, Phone, URL, Color, Time, Geolocation. See Text reference. |
Note | Multi-line text. Binds to Textarea or RichText. See Note reference. |
Number | Numeric. Binds to Number, Slider, Rating. See Number reference. |
Currency | Money. Binds to Currency. See Currency reference. |
Choice | Single-select. Binds to Choice. See Choice reference. |
MultiChoice | Multi-select. Binds to MultiChoice. See MultiChoice reference. |
Boolean | Yes/No. Binds to Boolean. See Boolean reference. |
DateTime | Date / date-time. Binds to Date, DateTime. See DateTime reference. |
Lookup | Related list pointer. Binds to Lookup, LookupControl. See Lookup reference. |
User | Person picker. Binds to User, PersonControl. See User reference. |
Taxonomy | Managed metadata. Binds to Taxonomy. See Taxonomy reference. |
URL (Hyperlink or Picture) | URL + label pair. Binds to Hyperlink. See URL reference. |
Image | Image column. Binds to Image field. See Image reference. |
Attachments | Item-level attachments. Binds to Attachments. See Attachments reference. |
Read-only column behaviour
Some SP column types are read-only by definition, Calculated and
system-managed columns like Created, Modified,
ID. SharePoint Forms365 detects these via the column's
ReadOnlyField flag and the runtime always renders them in read-only mode regardless of
any author override. The save flow strips them from the write payload to prevent SP from rejecting
the whole call. A Sealed column is not read-only: Sealed locks the column definition,
not its value, so Calendar base columns such as Start Time, End Time, Description and Location
remain editable.
How values write back
Values written to SP follow per-type shaping done by the field mappers in
src/core/sharepoint/fieldMappers/. The shaping is:
- Lookup, writes
{Field}Id: number(or{Field}Id: { results: [...] }when multi) - User, same
{Field}Idpattern - MultiChoice, writes
{Field}: { results: [...] } - Taxonomy, one term writes
{ Label, TermGuid, WssId: -1 }to{Field}; several terms write only the hidden note column. SharePoint maintainsTaxCatchAllitself - DateTime, ISO 8601 string
- Boolean, JavaScript boolean
- Currency / Number, plain number
You rarely need to know this, the field mapper handles it. The exception is when you write via f365.sp directly, in which case you need the SP shape.
Related
Related articles
- 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.
- Save flow, what happens when the user clicks Submit
The two-phase save pipeline, validation, primary write, then post-save writers for attachments, signatures, images, and child rows.