Known Issues for Sybase Unwired WorkSpace – Device Application Development

Workaround: Adjust the font or layout, or remove or add a line of controls, remove one line of controls.

When using a composite MBO relationship as a data source, when performing an operation on a child screen, you must always go through the parent screen or the operation fails.

When one child screen has two or more relationships with a parent and a create operation is submitted as pending through a composite relationship, and the user subsequently drills down through the other relationship to the child to perform a create operation, both fail to upload to server.

A failed create, update, delete on a composite relationship child causes the parent to be in pending status and the user sees that in the pending operation screen, but because its status is not create, update, or delete, it appears as "other."

Workaround: Manually create the links.

Workaround: This is designed as a convenience for the user. To change the list structure data, however, do not change the "copied" data directly, since the data—but not the list structure itself—is referenced by the previous record, and is changed if the previous record has not yet been submitted. The best method for working on a second record is to use delete and create instead of update.

Another workaround is to write custom code to clean up the controls after clicking Submit on the parent when you are done with the create operation.

Workaround: If the device client database throws this exception in a JOIN query, check your join fields to make sure they are the same type.

Although the default XSLT generator has been enhanced to add support for enforcing nullable/non-nullable values, the Remedy service is not honoring its own WSDL. When a column that uses an INT type (and cannot default to any value, as a string datatype can) is defined as not nullable, Remedy sends an empty value, causing the runtime to throw sync errors.

Workaround: Manually edit the XSLT file to set nullable to true on the column.

This problem is restricted to the emulator, and does not occur in the device itself. This error is caused by SQLite library, which handles applications installed on external storage memory differently than those installed in the main storage area.

Workaround: Install the application in the main storage memory of emulator, or test the application using an actual Windows Mobile device instead of the emulator.

When the active page is the FlowDesign page, and you change a device property (for example, a database page size) and device type (such as the BlackBerry 8800 or 9530) together, after you save the changes then change the device type again, you see a null pointer exception in error log, and the property is not changed. You cannot save the property if you then change another device property (a database page size) after you save the changes in above step.

Workaround: Before changing the property a second time, switch to the ScreenDesignPage and back to the FlowDesignPage and then administer the change.

Workaround: Change the attribute name for one of the MBOs so that the attributes are not identical.

Workaround: None.

Workaround: None.

Additionally, a mobile workflow application cannot perform an update of a NULL value where the definition of the update uses old values, for example:

UPDATE sampledb.dba.TravelRequest
SET
trvl_Status=:trvl_Status,
...
WHERE (trvl_Status = :old.trvl_Status)

In the above case, the NULL values are converted to an empty string, which causes the update to fail.

Workaround: None.