Cloud Integration and Boolean data fields
What is Boolean data type and why is it important with data mapping between two systems? Boolean is defined as having two values (usually displayed as either true or false), intended to represent the truth values of logic and Boolean algebra.
DSYNC can be used for deep integration purposes and therefore has the capability to handle different data types including Boolean.
If you do not need to send data to a system and it is a Boolean field we recommend you disable and do not sync the data element across. You do not have to sync all data fields. See the below video for a guide on how to disable data fields in mapping which you do not want to sync.
Boolean data type in DSYNC can have different representations which are user defined. You can change these from the boolean field settings.
Default representation is the standard true and false value which you know and expect. Apart from this, DSYNC allows you to choose a numeric representation and custom representation.
Numeric representation is handy when your source or destination system handles boolean data type as number. When you select 'Number' representation DSYNC treats 0 as FALSE, and 1 as TRUE.
Custom representation is a user defined textual value. Strings such as "Yes" and "No" can be used by some systems instead of the standard boolean values and DSYNC allows you to specify any string for True and False.
DSYNC validates given data values on source and destination against the field type set on individual fields. This includes boolean fields. Validation is based on the boolean field representation settings. So if you have a boolean field in data layout with numeric representation and the data which you are parsing is not numeric DSYNC will throw an error. More in depth video below.