For the complete documentation index, see llms.txt. This page is also available as Markdown.

Bulk row update and delete

For details about bulk editing in the table, refer to this section.

Bulk row update

Follow the instructions below to configure bulk table rows update:

  1. Select the Table component and navigate to the Row selection section in the right-side panel.

  2. There, select the Enable multiple rows selection checkbox.

  1. Create a new Condition action step and specify the following code: return {{ui.table.selectedRows.data.length>0}};

  2. For the if condition, add the Update Row action:

    1. In the Filters section, specify the identifier for updated records (we'll use row_number_id) - row_number_id in {{ui.table.selectedRows.data.map(item => item.row_number_id)}}.

    2. In the Configure row section, specify the parameter that will be updated (in our example, the record's status will change to Active).

    3. Select the Bulk Update checkbox.

  1. (Optional) For the else condition, you can configure an error notification.

  2. As a second step, add the Execute Action step and select the action that loads your data to display the updated values in the table.

  3. Add a toggle or button to the canvas and assign the bulk update action to its On Change/On Click trigger.

spinner

Bulk row delete

The flow here is similar to that of the Bulk update one:

  1. Repeat steps 1-4(a) from the Bulk update instruction above.

  2. For the if condition, select the Bulk Delete checkbox.

  3. (Optional) For the else condition, you can configure an error notification.

  4. As a second step, add the Execute Action step and select the action that loads your data to display the updated values in the table.

  5. Add a button to the canvas and assign the bulk delete action to its On Click trigger.

spinner

Prevent repeated execution

When a button triggers a bulk action, disable it while no rows are selected or while the action is running:

This reduces repeated execution while the action is running. Keep the Condition step as the main validation because the button state alone does not protect the database from an empty filter.

Last updated

Was this helpful?