Property reference

glide.rest.choice.allow_non_existing_value

Allows REST requests to set choice fields to values that are not defined as choices. When enabled, supplied values are accepted; the default is false, and the setting does not apply to the Change REST API.

Default
Not stated
Type
boolean
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? When true, this property lets REST requests set a choice field to a passed value even when that value is not defined for the field; it does not apply to the Change REST API.
What area does it affect? REST API choice fields
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? Review when REST integrations need to submit choice values not defined for a field.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name glide.rest.choice.allow_non_existing_value
Type boolean
Application Not stated
Default value Not stated
Description Enables passing non-existing values to a choice field. Does not apply to Change REST API /api/sn_chg_rest/change.

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
... APIs, only those APIs are available. • Type: string • Default value: all REST APIs are enabled by default • Location: Add the property to the System Property [sys_properties] table. glide.rest.choice.allow_non_existing_value Enables passing non-existing values to a choice field. Does not apply to Change REST API /api/sn_chg_rest/change. • Type: true | false • Default value: false If true, the choice field ...

More in glide.rest

Other properties in the same namespace.

All 28 properties in glide.rest →