Parameter and Argument Validation Rules and Error Messages

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.

The parameter name is invalid.

Enter a valid name.

Error: Invalid parameter name: '<Para Name>', name cannot be a Java or C# language.

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.

Shorten the parameter name to less than 100 characters.

Error: The argument '<Arg Name>' in operation '<Oper Name>' is not nullable and does not have a parameter mapped, thus it must have a default value.

A default value is not specified for the operation's parameter, which may result in a runtime operation failure.

Specify a default value for the argument.

Error: Attribute '<Attr Name>' cannot be mapped to more than one parameter.

An attribute has more than one Propagate to mapping.

Remove additional mappings.

Error: The data type of the parameter '<Para Name>' can not map to the data type of the argument.

The datatype of the parameter and the datatype of the argument do not match.

Warning: Parameter '<Para Name>' should not be nullable when it is mapped to a non-nullable argument.

The nullability of the parameter does not match that of the argument. For a non-nullable argument, the mapping parameter should also be non-nullable.

Change the parameter to non-nullable.

Error: Data type of the bound personalization key cannot map to the parameter: ‘<Para Name>‘.

Datatype mismatch.

Change the datatype of the parameter or the datatype of the personalization key so they match.

Warning: Parameter data length is shorter than the bound personalization key’s data length, value truncation might occur: ‘<Para Name>‘.

The length of the datatypes do not match.

Change the length of the parameter or that of the personalization key so they match.

Warning: A non-nullable parameter ‘<Para Name>’ cannot map to the nullable personalization key: ‘<PK Name>’.

A non- nullable parameter is mapped to a nullable personalization key.

Change the nullability of the parameter or that of the personalization key.

Warning: The maximum length of the operation parameter is different from the fill from attribute’s: ‘<Para Name>’.

The datatype lengths do not match. At runtime, when the attribute passes its value to the parameter, the value may be truncated.

Change the datatype length so they match.

Error: Binary parameter default value cannot exceed 16384 byte: ‘<Para Name>’.

The default value is too long.

Shorten the default value.

Error: Synchronization parameter ‘<Sync Para Name>’ cannot be mapped to more than one argument.

Two or more arguments map to the same synchronization parameter.

Change the mapping so only one argument maps to the synchronization parameter.

Error: Data type of the selected old value argument cannot map to the parameter ‘<Para Name>’ of operation ‘<Oper Name>’.

Datatype mismatch.

Change the datatype of the Old value argument or that of the parameter so they match.

Error: Argument ‘<Arg Name>‘ of type < Type>, does not allow length greater than <Arg Length>.

The argument length exceeds the maximum length allowed for its datatype.

Shorten the argument length to a valid length for the given type according to the message.

Error: Invalid default value ‘<Default Value>’ for the ‘<Type>’ data type: ‘<Arg Name>‘.

The argument default value is not valid for its datatype.

Change the default value to conform to the argument’s datatype.

Warning: Default value exceeds maximum length: ‘<Arg Length>‘.

The argument default value length exceeds the argument’s length.

Change the default value to conform to the argument’s length.

Warning: Non-nullable argument ‘<Arg Name>‘ cannot map to a nullable personalization key: ‘<Per Key Name>’.

A non-nullable argument is mapped to a nullable personalization key.

Change the nullability of the argument or the personalization key so they match.

Error: Invalid < object type > name: name cannot be empty.

The <object type> name cannot be empty.

Enter a valid value for the name of the <object type>.

Warning: Personalization key ''{0}'' with storage type ''{1}'' assigned to load argument: ''{2}'' will not be used because the mobile business object has a DCN cache policy.

Remove the Personalization Key mapping for the argument from the load arguments tab in the MBO Property view.

Error: If client parameter's data type is bigString/bigBinary or a structure type with bigString/bigBinary attributes, show as an error like "Structure '' < Structure name > '' contains field '' < attribute name > '' with data type '' < BigString/BigBinary > '', and cannot be used as a client parameter '' < client parameter name > .''

An error message displays if you generate a client parameter and use a structure that contains BigString/BigBinary field(s).

To provide client parameters for BigString/BigBinary datatypes, or a structure with BigString/BigBinary fields, use compatible types: String for BigString, Binary for BigBinary. For a structure, copy the original structure in WorkSpace Navigator, and change the large object type fields to String/Binary, then use the new structure as the datatype of the client parameter.

Error: Personalization key can’t be directly assigned to load argument: ‘<Arg Name>‘ of mobile business object which has a scheduled cache policy.

Do not use reserved parameters as an attribute name: count_bad_playback, error_category,error_message, last_good_playback, last_modified, last_playback, uagid, uapbk and uask.

Change the attribute name.