Account custom fields partial
Prepared custom-field controls shared by account and checkout forms.
Output: HTML partial.
This partial receives the local inputs below. It does not define a separate page view model.
Additional inputs
Section titled “Additional inputs”| Input | Type | Default / purpose |
|---|---|---|
| customFieldGroups | object[] | Prepared account or checkout custom-field groups; default empty array. Each group has fields[]. |
| customFieldsDisabled | boolean | false; disable controls without changing their values. |
| customFieldsFormId | string | Empty; optional owner form ID. |
Each field supplies key, customFieldDefinitionId, type, name, inputId, label, rawValue, displayValue, isEditable and isRequired. Select fields additionally supply options[]. Use the prepared groups from the current form context. Media controls in this package use the browser’s native file input; upload validation remains on the server.
See Custom-field structures for nested fields, types and the distinction between editable forms and order-address display groups.
Assets
Section titled “Assets”The reference package uses its bundled theme CSS, Bootstrap and theme JavaScript. Account and checkout controls use the bundled checkout script. Partials use their caller’s resolved assets.
Example
Section titled “Example”Resolve this partial after setting its documented inputs:
<cfinclude template="#request.resolveStorefrontView('partials/account_custom_fields.cfm', viewModel.theme.key)#">Navigation branches use cfmodule with their documented attributes instead of cfinclude.
Behaviour
Section titled “Behaviour”Use prepared form actions, field names and CSRF inputs from the reference implementation. Access checks, validation and commerce decisions remain outside the theme.