...
If there are multiple email address provided for one user AND those are separated by the MultipleEmailsDelimiter only the first email is imported if this configuration is present.
Reset Fields To Default If Empty Configuration
...
Sample Configuration:
| Code Block | ||
|---|---|---|
| ||
"ResetFieldsToDefaultIfEmptyConfiguration": {
"ResetFieldsToDefaultIfEmpty": [
"Vessel",
"Rank",
"EmbarkmentDate"
]
} |
If no value (null/empty) is provided for a user property and that property is part of field listed in the ResetFieldsToDefaultIfEmpty array, it resets empty value to its the user property (from no value) to the field’s default value (dependent on the data type - see below). But if that filed is
Any field not included in ResetFieldsToDefaultIfEmpty, that field is ignored doesn’t get updated and no value was provided (null/empty), will not be updated (ignored).
If we want to set null/empty value to any field, those fields must be included in ResetFieldsToDefaultIfEmptyConfiguration. That means If , if any organization uses deactivation field (Deactivate (X)) that needs to included in this configuration.
| Info |
|---|
The user property must be part of the |
Default value values for different user property types is as follows:
User scalar property (string): empty string (except any Primary Identifying Field)
OPF (single-choice-string): first choice
OPF (string): empty string
OPF (int): not supported yet (we don’t have a default value for int yet)
...