Help center Core configuration Automation, fields & notifications Configure custom fields and dropdown choices Updated Wednesday, October 28, 2026 · Marcel Gravelle Custom fields capture information that is specific to your support process across cases, customers, knowledge and assets. Stable field identities and deliberate types make the same information useful in forms, search, workflows and reports. Applies to: Supportbench Core. Location: Settings → Configuration → Custom fields. Editing requires Administer fields. Before you begin Decide where the data belongs and how agents will use it for diagnosis, filtering or reporting. A field name is not a substitute for a clear data definition.Choose Location and Type carefully before the first save. Existing identities and list-item IDs may be used by policies, views and workflows. Configure and verify Open Settings → Configuration → Custom fields and choose New Field.Choose Location and Type before saving. These are immutable for the saved field; changing the desired data model later is not a type conversion.Set Name, Label, Description, Active and Order. For a Case field, review the available Division scope and the other controls in the reference below.Choose Save Changes. For a supported dropdown, add each choice with New Item, then configure its name, Parent, Order and Active value and save the item.For Case fields, add the field to the intended Case Policy and save that policy. A field definition alone does not place it on every Case form.Open the relevant form as an intended agent, enter a controlled value and save the record. Reopen it and verify any dependent view filter, search or workflow separately. Settings reference Field identity and behaviorSettingWhat it controlsHow to chooseName / Label / DescriptionInternal name up to 50 characters, optional display label up to 22, and description up to 250.Use a concise label and explain how to enter a valid value.LocationThe entity or supported location using the field; locked after creation.Choose the intended entity before the initial save.TypeText box, dropdown, checkbox, multi-row text, URL, multi-select dropdown, Tags, Mapping or Date as available.Match the actual value and consuming forms. Changing type does not convert saved data.ActiveKeeps the field available for new data entry. Inactive fields retain stored values.Deactivate obsolete fields only after reviewing consumers.OrderDisplay order from 0 through 25.Group related inputs.DivisionsScope for Case fields, constrained by the administrator’s available divisions.Use global scope only when all relevant teams need the field. Restricted assignments can be preserved.Mapped Tags FieldFor Case Mapping fields, selects an active Company or Contact Tags field.Verify the target entity and tag meaning.Search indexingAvailable for supported text types on Case, Company and Contact fields.Enable where the field contains useful search terms. Dropdown choicesSettingWhat it controlsHow to chooseSave field / New ItemThe field must be saved before options can be managed.Create the stable field identity first.Choice nameDisplayed option text. Duplicate names are allowed; immutable item IDs distinguish them.Prefer unambiguous labels to reduce selection errors.ParentOptional hierarchy, with server-paged search for large lists.Review the existing branch before moving a choice.Order / ActiveOrder 0–25 and availability for new selections.Keep historical values while hiding obsolete options where appropriate.Parent changes / DeleteParent changes can move direct children back to the root. Field deletion retains stored values.Review the confirmation and all downstream consumers rather than assuming a destructive data conversion. Behavior to knowField IDs, types and list-item IDs are contracts used by other features. A label change is different from creating a new identity.Existing internal locations/types can be retained for compatibility even when they are not offered for new fields.Customer survey questions are configured separately in Custom fields survey. Recommended use Keep configuration names and descriptions clear for the people who will maintain them.Review related workflows, reporting and permissions before changing shared configuration. Worked example Define a Case dropdown Product area with choices Hardware and Software, using labels that agents can consistently apply.Save the field, create both active choices, and place the field on the intended Case Policy.Record Hardware on an approved sample Case and verify the saved value.Build or test the relevant filter using that actual field and choice. Renaming a label keeps its identity; creating another similarly named choice does not. Troubleshooting ProblemWhat to checkThe field is missing from the formCheck Active, Case Policy placement/visibility and applicable Division scope, then reopen the form.A dropdown has no choicesSave the field first, add supported choices with New Item and check each choice’s Active value.Type or Location cannot be changedThey are immutable for the existing field. Plan a separate data-model change and assess policies, reports and existing values before creating a replacement.A filter still uses an old choiceCheck the field and item IDs as well as display labels. A new similar label is not the same saved choice.I cannot edit fieldsCheck Administer fields. Related configuration Organization → Configure agent roles and division accessConfiguration → Configure workflows and automationFilter case views with custom fields and verify the resultsChoose and build the right support operations report Was this article helpful? Yes No Thank you for your feedback.