Allows the user to remove a row from a table control. Only valid when declared inside a table's row template.
Remarks
When the user clicks a removebutton,
the button's closest ancestor row in the parent table control will be removed, even if the
button itself is nested inside another control within the row
template.
The tableFootable control has a popup in each of its rows. Each
popup in turn contains a removebutton.
If the user clicks the removebutton, its closest ancestor
row in the XML hierarchy is removed, even across the complete
popup control.
The record of the affected row also gets removed from the parent table control's
recordset. The recordset query is, however, not
re-evaluated, and so all the other rows of the table stay in place.
The removebutton is invalid in a header or
footer row, since the user cannot remove headers and footers from a table
control.
Just like with the addbutton control, whenever the parent table control’s recordset is
re-evaluated for any reason after the user removed rows from it, the changes caused by the
removebutton will be discarded (that is, the removed rows will
reappear).
Sample
...
<table id="tableBoo"
recordset='{TABLE suspect1,
suspect2,
suspect3
("Tom", "Dick", "Harry";
"Hickory", "Dickory", "Dock";
"Eenie", "Meenie", "Miney Moe")}'
record="suspect">
<row>
<cell>
<textview text='{suspect.suspect1}'/>
</cell>
<cell>
<textview text='{suspect.suspect2}'/>
</cell>
<cell>
<textview text='{suspect.suspect3}'/>
</cell>
<cell>
<removebutton text="Go ahead, remove this row"/>
</cell>
</row>
</table>
...
A
3-row, 3-column table control with a removebutton included
in the row template.
Even though the table control in the above sample has an identifier, none
of its child elements do, so a workflow script running in the Mobilengine Cloud would only be
able to access the metadata of this form submission.