Process Hub · Fields, validation and calculations
Configure lookup choices and dependent field values
Use stable source keys and filters to keep related choices consistent.
On this page
Before you start
- Prepare an approved deployed lookup in Settings → Process Hub → Lookups. Know its key, display label and filter columns. Use synthetic customer/product data.
Lookups and assignments
Use a real single-select User field for assignments. A lookup returning someone’s name or email is not automatically a profile-user assignment.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open the process field in Builder and choose the prepared lookup source. Select a stable key column and a readable display label.
- Preview the source with a known sample. Confirm values resolve in the active profile and that the intended runtime users have the required access.
- For a dependent choice, open its filter controls and compare the source column with the parent field value. For example, filter contacts by the selected customer key.

Select the lookup field and review its source and available-choice filters in Question settings. - Configure any supported auto-populated target fields explicitly. Keep source and target types compatible; copying a friendly label does not establish a record relationship.
- Test changing the parent choice after choosing the child. Confirm the saved combination remains valid; clear and reselect a dependent value when the previous choice no longer applies.
- Save, publish and deploy the process. Test with a member account and a missing/disabled source row, then document who maintains the source list.
Example: customer and delivery contact
Customer C-100 has contacts CT-101 and CT-102; customer C-200 has CT-201. Select C-100 and confirm only its contacts appear. Change to C-200 and confirm the previous contact is not silently treated as valid.
What you should see
Users select relevant values from an approved source and dependent choices correspond to their parent selection.
If something goes wrong
The list is empty
Check profile, deployed lookup, source query/filter, permissions and whether the parent value is a stored key or a display label.
An old record shows an unresolved label
The saved key may no longer exist in the source or access may have changed. Investigate the original key before replacing data.