Mobile Business Object Validation Rules and Error Messages

Validation rules are enforced during development of the MBO and, in some cases, when you deploy the MBO to Unwired Server. Error/warning messages are generated when validation rules are violated.

Table 1. MBO validation error messages
Severity and message Action
Error: Invalid Mobile Business Object name: {0}.  
Error: Invalid {0} name {1},which cannot be a reserved attribute name. The reserved attribute name list is: inserted_at, last_modified, sequence_updated_at, ua_state, uabuid, uagid, uaseq, uask.

{0} is the name of the MBO, {1} is the name of the attribute.

Error: Invalid {0} name {1}, which cannot be a reserved parameter name. The reserved parameter name list is: count_bad_playback, error_category, error_message, last_good_playback, last_modified, last_playback, uagid, uapbk, uask.

{0} is the name of the MBO, {1} is the name of the parameter.

Error: Duplicate Mobile Business Object name: {0}.  
Warning: Invalid Syncable setting: {0}. If a Mobile Business Object has no attributes, it cannot be set ''Syncable''.  
Warning: Neither attribute nor operation is defined: {0}.  
Error: No attributes are defined: {0}. At least one attribute must be defined in the Attributes wizard, except for File MBOs, which have no such requirement.
Error : Invalid Mobile Business Object name '{0}' ,which cannot be a reserved attribute name . The reserved attribute name list is: inserted_at, last_modified, sequence_updated_at, ua_state, uabuid, uagid, uaseq, uask.
Error : Invalid Mobile Business Object name '{1}' , which cannot be a reserved parameter name . The reserved parameter Name List is: count_bad_playback, error_category, error_message, last_good_playback last_modified, last_playback, uagid, uapbk, uask.


Created September 17, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com