Covering the Playback and Synchronization Parameters of a Primary Read Operation

The result set of an alternate read operation must contain the playback and sync parameters of the mobile business object (MBO).

For an alternate read to be valid, its result set must include any MBO playback and sync parameters.

For example, create three MBOs by dragging and dropping the sampledb.dba.customer data source onto the Mobile Application Diagram. Modify the MBO definition with the following SQL statement, and set Filter by for both the "state" parameter and the "company_name" attribute.

SELECT id, fname, lname, address, city, state, zip, phone, company_name FROM
sampledb.dba.customer WHERE state=@OP["state"="CA"]

This simple example illustrates a validation error. Create an alternate read operation for each MBO using the SQL statements:

Customer1 MBO
```
select * from customer
```
This is valid, since the alternate read result set contains the "state" and "company_name" playback and sync parameters.
Customer2 MBO
```
select id, fname, lname, phone, company_name from customer where
company_name=@OP["company_name"="AAA"]
```
A warning displays since "id, fname, lname, phone, company_name" does not contain the "state" playback and sync parameter.
Note: Data in the @OP clause is not used for validation.
Customer3 MBO
```
select id, lname, fname, phone, company_name from customer where
state=@OP["state"="CA"]
```
This query also generates a warning. Although the read operation's parameter contains "state," the result set does not contain the "state" playback and sync parameter. It contains another sync parameter "company_name."