Type coercion

this document describes how {{product name}} behaves in situations when it receives values in expected and unexpected data formats when array is expected received description array the value is handed over unchanged other if the received value is not of the array type, {{product name}} will create an array and the first (and the only) element will be the received value when boolean is expected received description boolean the value is handed over unchanged number the value is converted to logical yes , even if the value is 0 text if the value is equal to false or the value is empty, it is converted to logical no if not, it is converted to logical yes other the value is converted to logical yes whenever the received value exists (is not null ) when buffer is expected received description buffer the value is handed over unchanged only if the codepage is as expected if the codepage differs, {{product name}} will try to convert the received value to the requested codepage if this conversion is not supported, {{product name}} will return a validation error boolean the value is converted to text ( true / false ) and then to binary data following the steps mentioned above for converting to text date the value is converted to iso 8601 text and then to binary data following the steps mentioned for converting to text number the value is converted to text and then to binary data following the steps mentioned above for converting to text text the value is converted to binary data and encoded as expected if the expected encoding is not specified, utf8 encoding will be used other {{product name}} returns a validation error when collection is expected received description collection the value is handed over unchanged other {{product name}} returns a validation error when date is expected received description date the value is handed over unchanged text {{product name}} will try to convert the text to a date if the conversion fails, it will return a validation error date must contain day, month and year date may contain time and time zone default time zone is based on your settings see these examples https //help make com/type coercion#rnpri number {{product name}} will treat the number as milliseconds since jan 01 1970 (utc) and convert it to a corresponding date other {{product name}} returns a validation error examples of date format 2016 06 20t17 26 44 356z 2016 06 20 19 26 44 gmt+02 00 2016 06 20 19 26+0200 2016 06 20 17 26 44 2016 06 20 2016/06/20 17 26 44 2016/06/20 19 26 44+02 00 2016/06/20 17 26 2016/06/20 5 26 pm 2016/06/20 06/20/2016 17 26 44 06/20/2016 19 26 44+02 00 06/20/2016 17 26 06/20/2016 5 26 pm 06/20/2016 20 6 2016 17 26 44 20 6 2016 19 26 44+02 00 20 6 2016 19 26 44+02 00 20 6 2016 when number is expected received description number the value is handed over unchanged text {{product name}} will try to convert the text to a number if the conversion fails, it will return a validation error other {{product name}} returns a validation error when text is expected received description text the value is handed over unchanged array if the given array supports conversion to text, the value will be converted if not, {{product name}} will return a validation error collection the value is converted to a json string an array of collections is converted separately to a comma separated list boolean the value is converted to text ( true / false ) buffer if text encoding is specified for binary data, the value will be converted to text if not, {{product name}} will return a validation error date the value is converted to iso 8601 text number the value is converted to text other {{product name}} returns a validation error when time is expected received description time the value is handed over unchanged text {{product name}} will try to convert time to the hours\ minutes\ seconds format if the conversion fails, it will return a validation error other {{product name}} returns a validation error