First/Subsequent Mobile Business Object Properties

First/subsequent mobile business object (MBO) properties available from the Properties view.

First MBO refers to the first MBO defined from a single EIS operation from which multiple MBOs can be defined. Subsequent MBO refers to any other MBOs defined from this operation. To ensure that the properties of the first and subsequent MBOs maintain synchronization, most subsequent MBO properties are read-only. The shared properties (definition, load arguments, and so on) of subsequent MBOs can be modified only through the first MBO.

Multiple MBO attribute properties
Property tab	First/subsequent MBO
Share	Identifies the enterprise information system (EIS) operation to which the MBOs are bound. The share tab appears for: Any MBO (except JDBC and REST) with multiple result sets. First MBOs with at least one subsequent MBO. Subsequent MBOs. The first MBO Share tab includes Add, Delete, and Delete All buttons, which you can use to add or delete subsequent MBOS. If you delete all subsequent MBOs, the first MBO reverts to a "normal" MBO. If a subsequent MBO is added to a normal MBO, the normal MBO becomes the first MBO in a first/subsequent MBO relationship. In other words, Unwired WorkSpace supports switching MBOs between normal and first MBOs.
Data source	Available only from the first MBO. Change Connection Profile – retains the first/subsequent MBO relationship. Bind Data Source – drops the first/subsequent MBO relationship and deletes all subsequent MBOs. The first MBO reverts to a normal MBO.
Definition	The definition only can be changed in the first MBO, other than the ability to modify subsequent result set filters. After changing the definition, Unwired WorkSpace attempts to match and merge the changes, which may include adding, refreshing, or deleting subsequent MBOs. First and subsequent MBOs share the same credential properties.
Roles	Subsequent MBOs inherit roles from the first (as defined in the wizard), but you can also add or modify roles for subsequent MBOs.
Load arguments	Available from the first MBO and is read-only for subsequent MBOs. For each MBO, the load argument can only propagate (propagate to attribute) to its own attributes.
Attributes mapping	Modify attribute mappings for subsequent MBOs independently of the first.
Object queries	Create object queries for subsequent MBOs independently of the first.
Cache group	First MBO and all its subsequent MBOs must be in the same cache group, but can be in different synchronization groups.