How to Combine Bulk Actions with Active Filters in TableCrafter

Updated July 2026 • 6 min read • By Fahad Murtaza • By Fahad Murtaza

When you are managing hundreds or thousands of Gravity Forms entries in a TableCrafter table, bulk actions and active filters are your two most powerful tools, but the real productivity unlock comes from using them together. Filtering down to a precise subset of rows and then running a bulk delete, export, or column-fill on exactly that set saves significant time and eliminates the risk of touching records you did not intend to modify. This guide walks through how the combination works, what to watch for, and how to configure your tables to get the most out of it. WordPress powers 43% of all websites globally (W3Techs, July 2026), and TableCrafter bridges the gap between the data you collect and the tables your users need to see, no custom PHP, no dashboard access required for viewers. The free version on WordPress.org supports CSV, JSON, Google Sheets, and Excel. Pro adds Gravity Forms, Airtable, Notion,. REST APIs handle over 83% of all web API traffic as of 2025 (RapidAPI, 2025).

How Does Understanding Bulk Actions in TableCrafter Work?

Pro Bulk actions are a Pro-tier feature. Once unlocked, three bulk operations are available on any TableCrafter table:

• Bulk Delete, permanently removes selected Gravity Forms entries via the GFAPI. This action cannot be undone from the table interface, so use it with care.
• Bulk Export, exports only the selected rows to CSV, Excel, or PDF, depending on your export configuration.
• Column Fill, writes a single value to a specific column across all selected rows. This is useful for status updates, category assignments, or any field that needs to be set uniformly across a batch of records.

Bulk actions appear as a checkbox column on the left side of the table and a dropdown menu above or below the table body. All bulk operations are processed through wp-admin/admin-ajax.php with nonce validation and WordPress capability checks, so permissions you configure at the table level are enforced on every bulk request.

How Active Filters Scope the Selectable Row Set?

Pro TableCrafter's advanced filter system lets visitors or administrators narrow the visible rows by field value, date range, multi-select category, or lookup field label. When a filter is active, the table re-fetches matching rows from the server via AJAX and renders only those rows in the table body.

The key behavior to understand: the checkbox column and bulk action selection always operate on the currently visible (filtered) row set. If you have 2,400 entries in a table and you apply a filter that returns 38 rows, the "Select All" checkbox selects those 38 rows, not all 2,400. This is intentional and is what makes the filter-then-bulk-act workflow safe and predictable.

Filters can be stacked. You might filter first by a status field, then narrow further by a date range, and then apply a bulk column-fill to the resulting slice. Each layer refines the set before you act on it.

How Do I Filter Down and Run a Bulk Action?

The workflow below assumes you have a Pro table configured with at least one filter column and bulk actions enabled.

1. Open the page containing your table. The shortcode [tablecrafter id="X"] (also accepted as [tablecrafter id="X"] or [tablecrafter id="X"]) renders the table for the current user's role.
2. Apply your filter or filters. Use the filter controls above the table to set the criteria that define the rows you want to act on. Wait for the AJAX reload to complete, the row count in the table header updates to confirm the filtered set size.
3. Verify the row set. Scroll through the visible rows to confirm the filter returned what you expected before selecting anything.
4. Select rows. Click the header checkbox to select all visible rows, or check individual rows manually. The bulk action toolbar activates once at least one row is selected.
5. Choose and confirm the bulk action. Pick Delete, Export, or Column Fill from the dropdown. For Column Fill, a secondary input appears to specify the target column and value. For Delete, a confirmation prompt appears before any data is removed.
6. Review the result. After the action completes, the table reloads. If your filter is still active, the table re-applies it automatically and displays the updated matching rows.

How Do I Configure Tables to Support This Workflow?

To get the most out of combined filtering and bulk actions, a few table-level settings are worth reviewing in the TableCrafter admin (TableCrafter → Tables → edit your table):

Enable the Right Columns as Filters

In the Columns tab of the table builder, toggle the "Filterable" option on each column you want to use as a filter control. Columns that hold categorical data, status, type, assigned user, are the most useful filter targets when paired with bulk actions. TableCrafter automatically renders dropdown filters for columns that contain a bounded set of values, including Lookup fields that resolve an ID to a label.

Set Per-Page Row Limit Appropriately

If you routinely bulk-act on more rows than fit on a single page, increase the per-page limit under the Display tab. Alternatively, if your filtered sets are consistently small (under 200 rows), loading all filtered rows at once eliminates the pagination-boundary issue entirely. This setting is per-table, so you can tune it independently for each table's use case.

Role-Based Permissions

Pro Under the Permissions tab, assign which WordPress roles can view the table, which can edit inline, and which can run bulk actions. A common pattern for team workflows is:

• Viewer roles, read-only; see all data, no checkboxes.
• Editor roles, inline editing enabled; bulk Column Fill available.
• Admin roles, full access including Bulk Delete and Export.

Column-level permissions can further restrict which fields an editor role is allowed to modify via Column Fill, preventing accidental overwrites of sensitive fields.

[tablecrafter id="12"]

Drop that shortcode on any page or post. The rendered output, including which bulk action controls appear, automatically reflects the current user's role and the permissions you configured.

How Do Common Patterns and Use Cases Work?

Here are a few real-world workflows that benefit from combining filters with bulk actions in TableCrafter:

Status Batch Update

Filter the table to show only rows where a status field equals "Pending Review." Select all. Use Bulk Column Fill to set the status field to "Approved." All matching Gravity Forms entries are updated via GFAPI::update_entry_field() in a single operation. If you have email alerts configured on that field, they fire per-entry as each record is updated.

Filtered Export for Reporting

Apply a date range filter to isolate entries from a specific month. Select all rows. Run Bulk Export as CSV or Excel. The exported file contains only the filtered rows, not the entire entry set. No manual copy-paste from a spreadsheet required.

Cleanup of Stale Records

Filter to entries older than a cutoff date with a status of "Abandoned." Review the filtered set. Select all and run Bulk Delete. Because the filter scopes the deletion to exactly the rows you reviewed, there is no risk of accidentally deleting active records.

How Do Troubleshooting Filter and Bulk Action Interactions Work?

A few issues come up occasionally when using these features together:

Bulk action processes more rows than expected

This usually means the "Select All" checkbox was clicked before the filter finished loading. Always wait for the AJAX reload indicator to disappear and confirm the row count before selecting. If the table auto-refreshes (the Auto-Refresh feature in Pro), be aware that a refresh mid-selection will clear your checkboxes, pause auto-refresh before running a bulk operation on a slow connection.

Filter resets after bulk action completes

TableCrafter preserves the active filter state across bulk action reloads by default. If your filter is resetting, check whether a page-level caching plugin is intercepting the AJAX response. NitroPack and similar tools sometimes need an exclusion rule for wp-admin/admin-ajax.php requests from the frontend.

Column Fill is not visible in the bulk action dropdown

Column Fill only appears when the current user's role has inline editing permissions on at least one column in the table. If the dropdown shows only Delete and Export (or nothing at all), revisit the Permissions tab in the table builder and confirm that inline editing is enabled for the role in question.