Mobile Business Object Errors

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

• Binding an MBO to a Database Fails
  Problem: Failed to bind a mobile Business object (MBO) to a non-Sybase database due to a missing JDBC driver.
• Multilevel Insert Operation Fails
  Problem: A multilevel insert operation fails on the device client.
• MBO Retrieves Incorrect Data
  Problem: The MBO does not retrieve the expected data on the device.
• Relationship Error
  Problem: Error occurs when trying to link multiple mobile business objects (MBOs) to a single child MBO.
• Warning Message When Creating Relationships
  Problem: When attempting to create a relationship between different types of MBOs, a warning message is displayed.
• Troubleshooting Default Values for Adaptive Server® Anywhere uniqueidentifiers
  Keep these points in mind when working with Adaptive Server Anywhere uniqueidentifiers.
• AutoCommit Option for JDBC MBOs Using an ASE Data Source
  When you create MBOs from Adaptive Server® Enterprise stored procedures that use temporary tables, you must select the AutoCommit check box in the New Attributes or New Operation definition screen.
• Passing an Empty String or Byte into a Required Binary Column in ASE
  When defining an MBO from an Adaptive Server Enterprise data source an error message displays if you pass an empty string or empty byte[] into a required binary column in ASE results in an ASE non-nullable column exception.
• Preview Errors for a Web Service Mobile Business Object with date/time Types
  Problem: You see an error when you are previewing a Web service mobile business object (MBO).
• Web Service Mobile Business Object Must Be Connected to Connection Profile
  Problem: The Web service connection profile must be connected to deploy, generate code, build packages, and so on.
• Refresh Fails Due to Missing Load Argument Default Values
  Problem: Adding load arguments with "Propagate to attributes" that have no corresponding datasource columns, then selecting Refresh, may fail due to missing load argument default values.
• Input Parameters Fail to Generate for Complex Data Sources
  Problem: For Web service and other data sources with very complex structures with deeply nested element trees, StackOverflow or OutOfMemory may occur, or some of the operation input parameters may not be generated properly.
• Output Mapping Warning Message for Multilevel Insert Operations
  Problem: A warning in the output mapping tab indicates that some output mappings are ignored when using the "Apply Output of ENTITY READ" operation cache policy.
• Attribute Length Set Incorrectly for Operation and Load Arguments
  Problem: Due to JDBC driver metadata retrieval related API limitations, Sybase Unwired WorkSpace does not always set the correct attribute length, especially for operation arguments and load arguments. For STRING and BINARY types, if the lengths are unknown, Sybase Unwired WorkSpace sets them to STRING(300) and BINARY(32767) by default, and gives a warning to adjust the length to avoid wasting device database space, and/or getting runtime data truncation.
• Unable to properly update the CDB because the partition was improperly assigned
  Problem: An MBO with a load/synchronization parameter, using an on-demand cache group interval greater than 0, and the load parameter does not have the "Propagate to Attribute" set:
• Syntax Errors When Creating a Database Mobile Business Object
  Problem: Calls from Sybase Unwired WorkSpace to the EIS during MBO creation/development cannot distinguish syntax from data errors.
• Sybase MBOs That Invalidate the Cache
  Problem: MBO operations bound to Sybase BAPIs that use the "Invalidate the cache" policy may not refresh the Unwired Server cache.