These validation rules apply to synchronization parameters and are enforced during MBO development, and, in some cases, when you deploy the MBO to Unwired Server or synchronize a device application. Messages are generated when validation rules are violated.
Severity and message | Cause | Action |
---|---|---|
Error: Data type of the bound personalization key cannot map to the parameter: '<Para Name>'. |
The datatype of the mapped personalization key differs from the datatype of the synchronization parameter, which may result in a synchronization failure. |
Change the datatype of the personalization key to match the datatype of the synchronization parameter to which it maps. |
Warning: Parameter data length is shorter than the bound personalization key’s data length, value truncation might occur: '<Para Name>'. |
Datatype length mismatch. |
Change the datatype length of the parameter or that of the personalization key so they match. |
Warning: Non-nullable parameter "ParaName" cannot map to the nullable personalization key: "PKName". |
A nullable personalization is mapped to a non-nullable parameter. |
Change the null-ability of the synchronization parameter or that of the personalization key so they match. |
Error: Invalid default value '<Default value>' for the ‘{1}’ data type: '<Para Name>'. |
The datatype of the default value does not match the given datatype. |
Specify a valid default value. |
Warning: Default value exceeds maximum length: '<Para Name>'. |
The default value is too long compared to the datatype's length definition. |
Enter a default value that is less than the maximum allowed. |
Error: Binary parameter default value cannot exceed 16384 byte: '<Para Name>'. |
The default value length is more than 16384 bytes. |
Shorten the default value. |
Error: The data types of the parameter '<Para Name>' and the ‘Mapped to’ attribute '<Attr Name>' should match. |
Datatype mismatch. |
Change the datatype of the synchronization parameter, or map it to a different attribute, or change the datatype of the attribute to which it maps. |
Warning: The null-ability of the parameter '<Para Name>' should be the same as the attribute it is mapped to. |
The null-ability of the parameter and the attribute to which it maps do not match. |
Change the null-ability of the synchronization parameter or that of the attribute so they match. |
Warning: The data length of the parameter '<Para Name>' is different from the data length of the its ‘Mapped to’ attribute '<Attr Name>'. |
Datatype length mismatch. |
Change the datatype length of the synchronization parameter or that of the attribute so they match. |
Warning: No ‘Mapped to’ attribute specified for synchronization parameter: '<Para Name>'. |
There is no Map to attribute defined for the parameter, which may lead to a synchronization failure. |
Specify a Map to attribute for the synchronization parameter. |
Error: Mobile business object '<MBO Name>' has more than one synchronization parameters that are mapped to multiple personalization keys. |
More than one synchronization parameter is mapped to multiple list type personalization keys. |
Remove any extra list type personalization key mappings. Only one synchronization parameter can be mapped to a list type personalization key. |
Error: Synchronization parameter '<Para Name>' of type {0}, does not allow length greater than {2}. |
The synchronization parameter length is too long: {0} may be STRING or BINARY {2} 8191 for STRING 32767 for BINARY |
Shorten the datatype length. |
Error: Invalid parameter name: '<Para Name>'. A valid identifier name must begin with an alphabetic character or an underscore, followed by alphanumeric characters or underscores. |
An invalid parameter name is specified. |
Enter a valid name. |
Error: Invalid parameter name: '<Para Name>', name cannot be a Java or C# language keyword. |
The parameter name is a Java or C# keyword, such as binary, boolean, byte, char, date, datetime, time, decimal, double, float, object, int, integer, long, short, string, switch, and so on. |
Do not use Java or C# keywords as parameter names. |
Error: Invalid parameter name: '<Para Name>', the length must be less than 100. |
The length of the parameter name is longer than 100 characters. |
Enter a name shorter than 100 characters. |
Error: Duplicate parameter name: '<Para Name>’. |
The name of the parameter is the same as an existing synchronization parameter. |
Enter a valid name. |
Error: Invalid '<Para Name>' name: name cannot be empty. |
No parameter name has been specified. |
Specify a valid name for the parameter. |
Warning: The length of synchronization parameter '<Parameter name>'' is not specified, set to <Default length> by default. Update the length to avoid truncation if necessary. |
If the parameter’s length is not specified, a default length is set. |
Specify the length. |
Error: Structure ''<Structure name>'' contains field ''<attribute name>'' with data type ''<BigString/BigBinary>'', and cannot be used as a client parameter ''<client parameter name>''. |
A structured client parameter can not contain a field of data type BigString or BigBinary. |
Change the parameter to use a structure that does not contain a large object data type. |
Warning: The length of argument ''<Argument name>'' is unknown, so the length of client parameter ''Client parameter" is set to <length> by default. Update the client parameter length to avoid data truncation if necessary. |
The client parameter was given a default length when the argument length is unknown. |
Update the client parameter length to avoid possible data truncation. |