Remapping Attributes and Parameters

The remap option generates new mappings for unmapped attribute columns or parameter arguments based on the metadata of the data source to which the mobile business object (MBO) is bound.

For MBOs that already have mappings, selecting Remap remaps parameters and attributes to the data source based on the new data source definition.

Remap is available from both the Attributes and Parameters tabs in the Properties view, and also affects how Preview refreshes attributes and parameters. Selecting Remap:

Queries the metadata for unmapped column or argument lists.
Creates new attributes or parameters for unmapped columns or arguments using metadata information (name, type, default value).
Generates new data source mappings for attributes or parameters.
Establishes "Fill from attribute" links for parameters.

In the Preview dialog, Remap works automatically when refreshing MBOs if the definition of the MBO changes. For example, after you change the definition in the Definition dialog and select Refresh, not only is the data source metadata refreshed, a remapping of any unmapped attributes/parameters is automatically performed based on the refreshed metadata.

You have an MBO with attributes bond 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 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. After you refresh, the "Address" attribute is unbound. Without remap, you would manually add attributes and map them to the columns in the tabular view. Selecting Remap creates the new attributes and maps them to the appropriate columns automatically based on the modified metadata.