a!toJson excluding null values.

RE: a!toJson excluding null values.

Mike Schmitt — Thu, 30 Mar 2023 12:46:14 GMT

In the documentation for a!toJson() it makes no mention of empty fields of other types being removed, particularly when "FALSE" is passed in for the "removeNullOrEmptyFields" parameter (even though that's also supposed to be the default behavior).

I'd suggest raising a support case with Appian to address this potential discrepancy. I'd expect (if you're very lucky anyway) they might slot this in for an enhanced "evolved version" where the new one contains the behavior you're after - since just changing this behavior in the existing version could potentially break current uses of the current version.

RE: a!toJson excluding null values.

Stefan Helzle — Thu, 30 Mar 2023 11:16:34 GMT

Interesting. I did a quick test, and casting the CDT to a Map before the transformation seems to include empty fields. Maybe you wanna test this.

a!toJson(
  cast(
    type!Map,
    'type!{urn:com:appian:types:AA}AA_Vehicle'(
      vehicleId: 1
    )
  )
)

RE: a!toJson excluding null values.

riyazn399986 — Thu, 30 Mar 2023 10:17:17 GMT

Yes, we do have specific requirement to pass attributes even though value of the attribute is null.

Is there any solution or work around for this issue?

RE: a!toJson excluding null values.

Stefan Helzle — Thu, 30 Mar 2023 08:13:32 GMT

Handling of non-populated field in JSON is a very controversial topic. There is no real right or wrong.

Do you have any specific requirement from the API you are talking to?

I recommend to not use old versions of functions for new developments.

RE: a!toJson excluding null values.

riyazn399986 — Thu, 30 Mar 2023 07:49:25 GMT

I am concerned if a!toJson_17r1 get deprecated in future.

RE: a!toJson excluding null values.

Harshit Bumb (Appyzie) — Thu, 30 Mar 2023 05:06:56 GMT

I think they just improved the definition of the function to remove the null values. How about keep using the a!toJson_17r1 function?