Troubleshooting Synchronization Errors

Use this topic to troubleshoot synchronization errors.

Problem	Solution
You receive an error message that the mobile business object is not deployed to the server when you try to synchronize the mobile business object on the device.	Ensure that: The MBO has been deployed to the target server. The package name of the target MBO is correct on the client. The MBO name used by the client is correct. The MBO has been set to "syncable" in the Unwired WorkSpace ( located on the MBO General tab of the Properties view).
Device synchronization returns no data. The sample code below describes a potential misconception regarding syntax of generated code calls. In this example, the customer_list_unit.xml which is used to auto-generate the class objects contains this section: <parameters> <parameter id="customer.param.city" usage="sync" name="city" /> </parameters> which indicates the class object which is created from the XML requires 'city' to be specified prior to syncing with the object. For example: >CustomerSynchronizationParameters params = Customer.getCustomerSynchronizationParameters(); >params.setCity("New York"); >params.save();	Verify that the MBO Filter By attribute is reflected on the client-side by the sync parameters. Specify a default value with the "default_value" attribute. For example: <parameter id="customer.param.city" default_value="New York" usage="sync" name="city" /> After making the change, regenerate the classes and re-synchronize the mobile business object on the device.

Problem

Solution

You receive an error message that the mobile business object is not deployed to the server when you try to synchronize the mobile business object on the device.

Ensure that:

The MBO has been deployed to the target server.
The package name of the target MBO is correct on the client.
The MBO name used by the client is correct.
The MBO has been set to "syncable" in the Unwired WorkSpace ( located on the MBO General tab of the Properties view).

Device synchronization returns no data.

The sample code below describes a potential misconception regarding syntax of generated code calls. In this example, the customer_list_unit.xml which is used to auto-generate the class objects contains this section:

</parameters>

which indicates the class object which is created from the XML requires 'city' to be specified prior to syncing with the object. For example:

>CustomerSynchronizationParameters params = Customer.getCustomerSynchronizationParameters();

>params.setCity("New York");

>params.save();

Verify that the MBO Filter By attribute is reflected on the client-side by the sync parameters. Specify a default value with the "default_value" attribute. For example:

After making the change, regenerate the classes and re-synchronize the mobile business object on the device.