Free cookie consent management tool by TermsFeed a!toJson() Function
a!toJson() Function

Function

a!toJson( value, removeNullOrEmptyFields )

Converts a value into a JSON string.

Parameters

Keyword Type Description

value

Any Type

The value to convert into a JSON string.

removeNullOrEmptyFields

Boolean

Determines whether fields with values that are null, empty strings, or empty arrays are removed from the JSON output. Default: false.

Usage considerations

Using the value parameter

The value parameter must be a CDT, a dictionary, a map, a record, or a list.

Using the removeNullOrEmptyField parameter

The removeNullOrEmptyFields parameter removes all fields with values that are null, empty strings, or empty arrays from the generated JSON request body. This is important for certain web services, such as those that follow the OData protocol. Some web services treat fields with null values differently from fields that aren't included in the request body at all. Omitting a field may mean "don't modify the field," while sending a null value for that field would mean "write a null value to the field."

The behavior of removeNullOrEmptyFields can also be leveraged for integrations that send a JSON request body by selecting the checkbox labeled Remove fields with null or empty values from generated JSON.

Feature compatibility

The table below lists this function's compatibility with various features in Appian.
Feature Compatibility Note
Portals Incompatible
Offline Mobile Incompatible
Sync-Time Custom Record Fields Incompatible
Real-Time Custom Record Fields Incompatible

Custom record fields that evaluate in real time must be configured using one or more Custom Field functions.

Process Reports Incompatible

Cannot be used to configure a process report.

Process Events Incompatible

Cannot be used to configure a process event node, such as a start event or timer event.

Old versions

There are older versions of this function . You can identify older versions by looking at the name to see if there is a version suffix. If you are using an old version, be sure to refer to the corresponding documentation from the list below.

Old Versions Reason for Update
a!toJson_17r1

Improved support for datetime values. This removes the need to create a supporting conversion rule.

To use the latest version of the function, replace the function with a version suffix with a new function reference.

To learn more about how Appian handles this kind of versioning, see the Function and Component Versions page.

a!toJson() Function

FEEDBACK