Mobile Business Object Errors

Provides information for problems you may encounter while developing mobile business objects.

• Troubleshooting MBOs
  Troubleshoot mobile business object (MBO) behavior problems.
• No Data or Images Appear on the Device
  Problem: No data or images appear on the mobile device.
• Troubleshooting Improperly Designed Mobile Business Objects
  Problem: Improperly designed MBOs can lead to mixed data from different users being returned to the device application.
• Database MBO Fails on Execution
  Problem: A database mobile business object (MBO) that worked during preview, fails (does not display table data) when it is deployed and executed.
• Web Service MBO Sync Exceptions After an Interface Change
  Problem: After changes are made to a Web service interface, you see sync exceptions and related errors in the client log. Server log errors may also indicate that Unwired Server did not recognize the value of HTTP Header SOAPAction: http://sybase.com/getPersonalKey.
• Binding an MBO to a Database Fails
  Problem: Binding a mobile business object (MBO) to non-Sybase database fails.
• Structure MBOs Not Automatically Generated After Rebinding
  Problem: When rebinding an MBO, Unwired WorkSpace keeps the existing parameters, so you must manually create parameters, set correct data type for the parameters, then map the parameters to the new arguments. But if the argument is a complex (structured) type created during the rebind, Unwired WorkSpace cannot automatically generate the new complex type, and the user cannot set the new complex type to a parameter which causes parameter and argument mapping failure.
• Multilevel Insert Operation Fails
  Problem: A multilevel insert operation fails on the device client.
• Search Errors and the RTRIM Function
  Problem: When performing a search with "equals" and "ends with" search criteria, you see an Unable to find... message on the device at runtime.
• Update Operation Fails
  Problem: An update operation fails if set maxlength for the attribute is less than the length in the enterprise information (EIS) database column.
• Relationship Error
  Problem: A mobile business object (MBO) with multiple relationships to a single child MBO reports an error.
• SQL Statement Yields Unexpected Results
  Problem: A SQL statement yields unexpected results in runtime.
• Warning Message When Creating Relationships
  Problem: When attempting to create a Mobile Business Object (MBO) relationship from the palette, a warning message is displayed.
• Synchronization Fails if Binary Attributes Have Unspecified Length
  Problem: Synchronization failures may occur for attributes with binary data types if no length is specified.