Synchronizing data successfully requires the correct development, configuration, and customization by the developer, administrator, and user. Each role has a unique task in the synchronization workflow.
This property is selected by default. If Syncable is not checked, the data for this object cannot be synchronized.
For each parameter you can specify a default value, whether a value is required, from where the value of the parameter is retrieved, and so on.
Typically, Unwired Server retrieves data from a data source when a device user synchronizes. However, if an administrator wants to preload data for a mobile business object, a data refresh should be scheduled. Preloaded data is available when a mobile-device user synchronizes, speeding up the process because Unwired Server does not need to check the data source for changes first.
The Unwired Server administrator can initiate synchronization between the server and device applications by setting up subscriptions for the clients. When a device application receives a notification from the subscription, the application can download the new data to the device.
When a subscription notification is generated, Unwired Server retrieves data from the data source and saves it in the server cache. If new data exists for a mobile-device subscriber, and "push" is enabled in the subscription, the server notifies the client; if either no new data exists or "push" is disabled, no notification is sent.
If a mobile business object has been reconfigured with the Syncable property, the entire deployment package that contains the modified mobile business object must be redeployed. In this case, the administrator should choose Replace as the deployment behavior, otherwise the property is not updated correctly.