Question 1

What causes setValue Not Persisting on GlideRecord?

Accepted Answer

setValue() called in 'after' Business Rule without second update()high likelihood

Check if your Business Rule has 'When' set to 'after' in the Business Rule form. After rules run post-commit, so setValue() changes exist only in memory unless you call gr.update() again.

Another 'before' Business Rule overwriting your setValue()high likelihood

Navigate to System Definition > Business Rules and filter by table name. Look for other 'before' rules with higher Order values that might be setting the same field after your rule runs.

Using setDisplayValue() instead of setValue() for reference/choice fieldsmedium likelihood

Check your code for setDisplayValue() calls on reference fields or choice fields that store sys_ids or internal values. The display value may not match a valid internal value.

Field is read-only or has database constraint overriding setValue()medium likelihood

Navigate to System Definition > Tables & Columns, find your table and field. Check if 'Read only' is true or if there's a database default value configured that's overriding your setValue().

GlideRecord object is stale or pointing to wrong recordlow likelihood

Verify your GlideRecord query returns valid results and current.sys_id matches the record you expect to update. Check if you're reusing a GlideRecord object after it's been modified elsewhere.

Question 2

How do you fix setValue Not Persisting on GlideRecord?

Accepted Answer

How to fix it Navigate to System Definition > Business Rules and open your Business Rule. Check the When field. If it's set to after, you need to call gr.update() after your setValue() calls. If in an after rule, modify your script to: current.setValue('field_name', 'value'); current.update(); If it's a before rule, check for conflicting Business Rules by filtering System Definition > Business Rules by your table name. Sort by Order and look for other before or before rules with higher Order values that modify the same field. If found, either adjust the Order of your Business Rule to run last, or modify the conflicting rule's condition to avoid overwriting your value. For reference fields, verify you're using setValue() with the sys_id, not setDisplayValue() with the display name. Check field permissions by navigating to System Definition > Tables & Columns and searching for your table and field name. Verify the field's Read only checkbox is unchecked and no Default value is conflicting with your setValue(). Add logging to verify your setValue() is executing: gs.info('Setting field to: ' + value); current.setValue('field', value);

Question 3

How do you prevent setValue Not Persisting on GlideRecord?

Accepted Answer

Always use 'before' Business Rules for setValue() operations unless you specifically need post-commit processing. Set Business Rule Order values explicitly (100, 200, 300) to control execution sequence when multiple rules affect the same table. Use setValue() for sys_ids and internal values, setDisplayValue() only for user-friendly display values that you're certain exist in the target table. Add condition checks in Business Rules to prevent unnecessary execution: if (current.field.changes()) { setValue logic here } Test Business Rules in sub-production instances first and verify field changes persist by querying the record directly after the transaction.

setValue Not Persisting on GlideRecord

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge

Related Articles