Skip to content
Astera Technology

Pick a record with a listbox or a result table?

Compare simple option selection with a lookup that needs several fields and separate record actions.

Choose against the task constraints

A buyer must select a supplier account. Two records have the same trading name but different account IDs and branches. Users also need a separate view-details link before choosing. A simple list of three delivery modes has no embedded action and should not inherit this complexity.

Decision worksheet
ConditionPlain listbox optionsResults with explicit row actions
One plain option labelSuitable selection model when fully implementedMay introduce unnecessary columns
Record identity needs several fieldsLong labels can become hard to compareSeparate columns retain account and branch identity
Link or button inside each resultInteractive descendants are not supported by listbox option semanticsKeep details and choose actions explicitly separate
Download editable CSV ↓

Use a lookup table with named details and choose actions for these supplier records. Do not mark a table full of interactive links as a plain listbox to imitate its appearance. A simple delivery-mode selector can remain a simple control.

Name alone is not record identity

Synthetic task cases
AccountTrading nameBranch
SUP-011Sample SupplyNorth branch
SUP-027Sample SupplySouth branch
SUP-052Other SampleCentral branch
Download editable CSV ↓

The requested account is SUP-027. Can the picker select the first matching trading name?

Show the worked answer

No. SUP-011 has the same trading name but is a different account. Select SUP-027 using the displayed account identity and branch context.

Check the chosen interaction

  • Details and choose actions name their associated record.
  • Keyboard use can reach each required action.
  • Selection persists by account ID, not its current name.

Related resources

UX/UI design services →