Defining Synchronization Properties for Individual Mobile Business Objects

Each mobile business object (MBO) that can be synchronized includes a Synchronization tab from which you configure synchronization behavior.

1. From the Mobile Application Diagram, right-click the MBO for which you are configuring synchronization, and select Show Properties View.
   Note: MBOs not bound to a data source do not support synchronization.
2. In the Properties view, select the Synchronization tab.
   Note: If you do not see the Synchronization tab, switch to the Advanced Developer profile.
3. Complete the synchronization definition:
   Use the Add, Delete, and Delete All buttons to create or remove parameters. You can also supply additional parameter information for each parameter, including:

   • Parameter name – by default each new parameter name is parameterN (N is the number of the parameter), which you can change.
   • Datatype – the datatype of the parameter. Datatypes in the Personalization key and Mapped-to columns must be compatible with the datatype selected here.
   • Nullable – accepts null as a valid value. Unselect this option if the argument to which this parameter is mapped does not support null as a valid value.
   • Default value – optionally select null as a valid value.
   • Personalization key – maps the synchronization parameter to a personalization-key value. If you specify a Personalization Key, the client is not required to provide a value, but must define a personalization value for the key before successfully using the MBO.
   • Mapped to – maps the synchronization parameter to an existing attribute.
   • Query limiting – limits synchronization to the last value entered by the device application user. For example, if unselected, default behavior of a query that uses this synchronization parameter:

     select * from Customer where customer.state = :state

     is:
     1. The device application user enters CA, then synchronizes. The application displays all CA customers.
     2. The user then enters NY and synchronizes, which displays CA and NY customers.
     If you select Query limiting, when the user enters NY the second time, the device application displays only NY customers.
     Note: Any attributes or load parameters designated as primary keys are automatically added to the Parameters section as part of the customized download data definition.
4. Select Customized download data to generate the SQL statement that defines synchronization. Unselecting this option clears the statement.
   By default, the internally generated SQL statement, based on the synchronization parameters, includes only the '=' operator. For any MBO that is bound to a JDBC data source, that includes a where clause operator other than '=' (for example, > , < , < > , != , > =, < =, ! > , ! <, and so on), follow these steps to properly generate the SQL statement :

   1. Unselect Query limiting.
   2. After selecting Customized download data, update the generated SQL statement. For example, change the '=' operator to '&gt'.

• Understanding Synchronization Parameters
  Synchronization parameters restrict the rows that are transferred from the consolidated database (CDB) to the device to match values the client provides. A synchronization parameter does not affect enterprise information system (EIS) interaction with the CDB, unless you specify the Synchronization Parameter setting for a given load parameter.
• Synchronization Parameter Definition Guidelines
  Understand guidelines and restrictions when defining synchronization parameters.