How do I Get Display Value in a ServiceNow client script?

g_form.getValue('assigned_to') returns the sys_id. To read the label the user actually sees, use g_form.getDisplayValue('assigned_to') — or on older releases g_form.getDisplayBox('assigned_to').value. For choice and reference fields those two calls return different strings, so never compare a display value against a sys_id.

How do I Get Reference Field Value in Client Script

g_form.getValue('caller_id') gives you the sys_id. To read fields on the referenced record, use g_form.getReference('caller_id', callback) with a callback so the lookup is asynchronous, or — better for one or two fields — call a client-callable Script Include with GlideAjax. Never call getReference() without a callback: it blocks the browser on a synchronous request.

How do I Dot-Walk in a ServiceNow Client Script

g_form.getValue('caller_id.department') returns nothing — g_form only knows fields that are on the form, so there is no client-side dot-walk. Get the related value one of three ways: add the dot-walked field to the form (fastest, no code), g_form.getReference() with a callback for several fields on the referenced record, or GlideAjax to a client-callable Script Include for anything deeper than one hop.

How do I Debug a Client Script in a ServiceNow client script?

Client scripts run in the browser, so debug them there: open DevTools, add a debugger statement or console.log at the top of the function, reload the form, and step through. Confirm the script is actually running before you suspect the logic — the usual culprits are a wrong script type, a mismatched table or field, an inactive record, or an early return from the isLoading guard.

How do I get display values, read reference field values, work around dot-walking limits and debug a ServiceNow client script?

Get the display value in a client script — g_form.getValue('assigned_to') returns the sys_id. To read the label the user actually sees, use g_form.getDisplayValue('assigned_to') — or on older releases g_form.getDisplayBox('assigned_to').value. For choice and reference fields those two calls return different strings, so never compare a display value against a sys_id.

Get a reference field value in a client script — g_form.getValue('caller_id') gives you the sys_id. To read fields on the referenced record, use g_form.getReference('caller_id', callback) with a callback so the lookup is asynchronous, or — better for one or two fields — call a client-callable Script Include with GlideAjax. Never call getReference() without a callback: it blocks the browser on a synchronous request.

Dot-walk in a client script — g_form.getValue('caller_id.department') returns nothing — g_form only knows fields that are on the form, so there is no client-side dot-walk. Get the related value one of three ways: add the dot-walked field to the form (fastest, no code), g_form.getReference() with a callback for several fields on the referenced record, or GlideAjax to a client-callable Script Include for anything deeper than one hop.

Debug a client script — Client scripts run in the browser, so debug them there: open DevTools, add a debugger statement or console.log at the top of the function, reload the form, and step through. Confirm the script is actually running before you suspect the logic — the usual culprits are a wrong script type, a mismatched table or field, an inactive record, or an early return from the isLoading guard.

How-To Hub

CLIENT SCRIPT
HOW-TO.

The four client-script tasks people actually search for — display values, reference field values, dot-walking limits, and debugging. Each guide opens with a direct answer, then numbered steps with copy-ready g_form and GlideAjax code.

Pick a task

Guide 1Get the display value in a client scriptUse g_form.getDisplayBox('field').value or g_form.getDisplayValue('field') to read what the user sees, and getValue() for the sys_id — with copy-ready onChange code.Read guide →
Guide 2Get a reference field value in a client scriptRead reference fields with g_form.getValue for the sys_id, getReference for the whole record, or GlideAjax for one field — with async callback code you can copy.Read guide →
Guide 3Dot-walk in a client scriptg_form cannot dot-walk. Use getReference with a callback, GlideAjax, or a dot-walked form field to read caller_id.manager.email safely from the client.Read guide →
Guide 4Debug a client scriptDebug client scripts with the browser console, debugger breakpoints, g_form.addInfoMessage, JS debugger logs and field messages — a repeatable checklist.Read guide →

Sibling clusters

Client scripts rarely stand alone — these hubs cover the server and automation halves of the same interview topics.