Modifying Load Arguments

Manage certain aspects of load arguments such as mapping them to synchronization parameters or personalization keys.

Use load arguments to control data refresh, create partitions, and, if mapped to a synchronization parameter, filter data that is returned to the mobile device. If you drag and drop a data source, or otherwise create MBO attributes that automatically generate attribute parameter-to-argument mapping, steps 1–3 below are optional. Do not confuse load arguments with operation arguments, which are defined or modified for individual operations.

In the Mobile Application Diagram, right-click the MBO, and select Show Properties View. Alternatively, click in the MBO title header to open the associated MBO properties view.
In the Properties view, select the Attributes tab, then select the Load Arguments tab.
Any arguments defined as part of the MBO definition automatically appear as load arguments, and you cannot arbitrarily add new arguments. For example, if your MBO is bound to the sample database's customer table, and the SQL definition is:
```
SELECT customer.id,   
         customer.fname,   
         customer.lname,   
         customer.address,   
         customer.city,   
         customer.state,   
         customer.zip,   
         customer.phone,   
         customer.company_name  
    FROM customer  
   WHERE customer.state = :state_name
```
then state_name is a load argument and state is the Propagate to attribute. You can modify load arguments from the Load Arguments tab.

For each argument, you can specify:

Property	Description
Data Source
Argument	Data source argument name to which the load argument is mapped.
Datatype	Datatype of the data source argument to which the parameter is mapped. You can change the argument's datatype only if the MBO is bound to a JDBC data source.
Nullable	Select this option only for data source arguments that support NULL as a valid value.
Value
Propagate to attribute	(Optional) Select an attribute to use its value for that of the argument. Note: When the MBO belongs to a cache group that uses an Online policy, the selected attribute is used as the query parameter of the automatically generated findByParameter object query.
Personalization key	(Optional) You can select a personalization key to map to the argument, which provides an argument value. For example, you can create and specify the "state" personalization key, and return values that match a specific value, such as "California." If Synchronization parameter is selected, this option is unavailable.
Synchronization parameter	(Optional and unavailable for MBOs in cache groups that use an Online policy) Map the load argument to an existing synchronization parameter (defined from the Synchronization tab) to use the synchronization parameter's value to refresh and filter data between the EIS and CDB, and download to mobile devices. See Combining Load Arguments and Synchronization Parameters for details. The Default value and Personalization key options are ignored if you select synchronization parameter.
Default value	(Optional) Enter a default value for the parameter. If Synchronization parameter is selected, this option is unavailable.