Listview controls are bound to a list key, however, the listview may only display a subset of that list key's child keys.
For example, when you have created a listview screen by dragging and dropping a mobile business object (MBO), you get a list key that has child keys bound to attributes and child keys bound to the create, update and/or delete operations' parameters. The listview, however, displays only the keys bound to attributes.
If you create a row using parameters bound to attribute keys, you get a new row with non-empty values visible in the listview. If you create a row using parameters bound to parameter keys, you get a new row with empty values visible in the listview, the non-empty values are in keys not displayed in the listview. For some MBO operations it would not be advisable to bind parameters to attribute keys (for example, an MBO with first_name and last_name attributes and a create operation that had one full_name parameter); but for many MBO operations, specifically those automatically generated for MBOs with database backends, it is appropriate.