...
| Code Block | ||
|---|---|---|
| ||
"DataValidationConfiguration": {
"IdentifierFields": [
{
"Name": "OrgLoginId",
"Type": "String"
}
],
"CriticalFields": [
{
"Name": "VesselEmbarkmentDate",
"Type": "DateTime"
"Format": "Stringdd-MM-yyyy"
},
{
"Name": "FirstName",
"Type": "String"
},
{
"Name": "LastName",
"Type": "String"
},
{
"Name": "Rank",
"Type": "String"
}
],
"RegularFields": [
{
"Name": "EmailAddress",
"Type": "EmailAddress"
},
{
"Name": "DeptCode",
"Type": "String"
},
{
"Name": "Password",
"Type": "String"
}
]
} |
...
Every field must have a Name and Type (String, DateTime, EmailAddress).. If any field is configured as “DateTime“ type then Format must be specified (example above) otherwise it will be considered as configuration error.
Also If UserImporterConfiguration contains DataFormattingConfiguration and it formats any datetime field, then the Format in DataValidationConfiguration for the datetime type field must match the output format of FieldFormatting.
| Code Block |
|---|
"DataFormattingConfiguration" : {
"FieldFormatting" : [
{
"FieldName" : "EmbarkmentDate",
"Type" : "DateTime",
"InputFormat" : "dd-MMM-yy",
"OutputFormat" : "yyyy-MM-dd"
}
]
} |
List of all exact names for user scalar properties which can be used:
...