Creating and customizing tables and data →mediumMultiple ChoiceObjective-mapped

SNOW-CAD Creating and customizing tables and data Practice Question

Exhibit

current.u_field.setValue('test');
current.update();

Refer to the exhibit. A developer wrote this script in a Business Rule on the 'incident' table. The script runs but the 'u_field' value is not saved. What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The u_field is defined as read-only

If the 'u_field' is defined as read-only (e.g., via dictionary attribute or ACL), the setValue method fails silently, meaning the value is not saved but no error is thrown. Option A is incorrect because the script appears syntactically correct. Option B is incorrect because setValue does exist on GlideElement. Option D is incorrect because setValue is the appropriate method for setting field values; setDisplayValue is used for setting display values, not database values.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The script has a syntax error
Why it's wrong here
The syntax is valid.
✗
The setValue method does not exist on GlideElement
Why it's wrong here
GlideElement does have a setValue method.
✓
The u_field is defined as read-only
Why this is correct
Read-only fields ignore setValue.
✗
The method should be setDisplayValue, not setValue
Why it's wrong here
setValue is used for stored values.

Visual reference

Go deeper

SNOW-CAD Creating and customizing tables and data Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question