Skip to main content

Date and time editors

FDC separates date, time, and date-time editing so each control matches the corresponding dataset field type.

Date and time editors
Loading FDC sample…
Column(
  children: [
    FdcDateEdit(
      dataSet: customers,
      fieldName: 'registered_at',
      label: 'Registered',
      showPicker: true,
    ),
    FdcDateEdit(
      dataSet: customers,
      fieldName: 'renewal_date',
      label: 'Renewal date',
      showPicker: false,
    ),
    FdcTimeEdit(
      dataSet: customers,
      fieldName: 'support_from',
      label: 'Support from',
      showPicker: true,
    ),
    FdcTimeEdit(
      dataSet: customers,
      fieldName: 'support_until',
      label: 'Support until',
      showPicker: false,
    ),
    FdcDateTimeEdit(
      dataSet: customers,
      fieldName: 'next_follow_up_at',
      label: 'Next follow-up',
      showPicker: true,
    ),
  ],
);

Date​

FdcDateEdit(
  dataSet: orders,
  fieldName: 'order_date',
  label: 'Order date',
  showPicker: true,
)

Time​

FdcTimeEdit(
  dataSet: appointments,
  fieldName: 'start_time',
  label: 'Start time',
  showPicker: true,
)

The time editor does not show a picker by default, so set showPicker: true when the picker is useful for the workflow.

Date and time​

FdcDateTimeEdit(
  dataSet: shipments,
  fieldName: 'scheduled_at',
  label: 'Scheduled at',
  showPicker: true,
)

Parsing and formatting​

All three controls use FDC date-like parsing and display formatting. A local formatSettings value can override the resolved application formatting for a specific editor.

The stored value remains typed; display formatting is not the persistence format.

Picker and keyboard entry​

The picker is an additional input path, not a replacement for typed entry. Users can enter a valid textual value, use the picker, or move through the form with the keyboard while the editor stays bound to the same dataset field.