Global Data Substitution replaces missing data with an empty string. This seems to work fine, if the missing data is undefined, but not if it is null.
null values occur a lot in the response of the Site API, if a custom field in Site Service is left empty.
Current behavior: A value of null is substituted as a string "null".
Desired behavior: The field value (after substitution) is falsy (i.e. an empty string).
Benjamin Hogl
Hi Benjamin,
Thanks for submitting this. This behavior looks more like an unintended behavior, or a bug rather than an aha idea. We're evaluating when we can get this fixed. For now we'll keep this as aha idea and in cosideration state.