Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property configures the truncation behavior for large request payloads, allowing for safer handling of multi-byte characters in the database. |
| What area does it affect? |
Database request handling |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review this property when adjusting limits for large API request payloads or addressing data truncation issues. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
glide.db.truncate_utf8 |
| Type |
boolean |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... column length to prevent data loss" Data type: String was_truncated Flag that indicates whether request data was truncated during persistence. You can change the default number of characters supported using glide.db.truncate_utf8 system property as described in the Additional information section. Valid values: • true: Request data was truncated during persistence. • false: Request data was not truncated during persistence. © 2026 ...
Context preview
Snippet 2
... characters. When truncation occurs, a was_truncated flag is set to true in the API response, with details provided in the truncation_message field. You can adjust the default limit using the glide.db.truncate_utf8 system property. • Coverage data is subject to database field length constraints. Fields affected include test_suite_results, test_results, and metadata_info JSON arrays. • Code coverage only includes code executed by the ...
More in glide.db
Other properties in the same namespace.
All 59 properties in glide.db →