Refreshing Attributes and Arguments

The refresh option generates new mappings for attribute/columns or operation arguments/load arguments based on the metadata of the data source to which the mobile business object (MBO) is bound

For MBOs already bound to data sources, selecting Refresh refreshes and/or remaps operation arguments, load arguments, and attributes based on the EIS data source metadata changes. Refresh also affects how Preview refreshes attributes and operation arguments. Internally, selecting Refresh:
Input and Output Mapping pages – refresh does not actually update metadata from the EIS. In order to get current metadata, the MBO developer edits the operation definition: it is not necessary to make any changes, just open the Edit Definition dialog, and click OK. At that point, a refresh prompt appears. Choosing:
You have an MBO with attributes bound to a database table defined as:
Customers[ID, Surname, GivenName, Address, Phone]
As the developer, you want to eliminate the “Address” column and better represent the address information. You modify the EIS database schema to:
Customers[ID, Surname, GivenName, Street, City, State, Country, PostalCode, Phone]
The MBO attributes become out of date because of the schema change, requiring the developer to Refresh the metadata. Note that after you refresh, the "Address" attribute is unbound. You can manually add attributes and map them to the columns in the tabular view, or select Remap to create the new attributes and map them to the appropriate columns automatically based on the modified metadata.