Use this topic to troubleshoot device applications.
When you create a relationship to a mobile business object, it creates a "filter by" on the child object. This child mobile business object can no longer be used to retrieve all items because it has a "filter by."
If there is a structured parameter in an operation, such as create, update, or delete, the Device Application Designer "flattens" that structured parameter out to a single row for the parameters. This means you can set only one row in the table inputs.
For example if a mobile business object has an operation create-customer with these parameters:
name phone orders[] id, description, quantity
then the device application shows it as:
name phone orders.id orders.description orders.quantiy {submit}
This means that you can create only one order in this form.
Workaround: Convert the structured parameters to regular parameters by changing the "." to "_" manually.
Problem: If you update operations on a child mobile business object and synchronize the parent mobile business object, the updated data is displayed correctly on the parent mobile business object, but a pending status records still displays on the child mobile business object. This also affects table and list detail mobile business objects.
Workaround: If the mobile business object to which you are adding a synchronization action has a child mobile business object, you must add a Refresh action to the screen of the child mobile business object so that the screen refreshes with the updated data.