How to Inline-Edit Lookup (Dropdown) Fields in a WordPress Table

Updated July 2026 • 7 min read • By Fahad Murtaza

A lookup field in TableCrafter is a table column whose editable state renders as a dropdown populated from a data source, either another Gravity Forms form's entries, a static options list you configure in the table builder, or a WordPress user list. When done right, lookup fields eliminate free-text errors and create consistent, validated dropdown experiences directly inside the table cell. When done wrong, you get the dreaded "Loading options..." spinner that never resolves. This guide covers the setup and the debugging path. 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, and no per-row limits on the free tier. The free version on WordPress.org supports CSV, JSON, Google Sheets, and Excel. Pro adds Gravity Forms, Airtable, Notion, WooCommerce, REST. Google Sheets is used by over 1 billion people globally (Google, 2023).

What Makes a Field a Lookup Field?

TableCrafter automatically treats certain Gravity Forms field types as lookup fields when inline editing is enabled:

• GF Select (Dropdown): Options are pulled from the field's GF choices configuration
• GF Radio Buttons: Treated the same as Select, renders as a dropdown in the cell
• GF Checkboxes: Renders as a multi-select dropdown (Pro only)
• Configured Lookup Column: Any column you explicitly configure as a lookup in the TableCrafter column settings, pointing to another form or a static list

Text fields and number fields are never lookup fields, they render as plain input boxes. The field type in Gravity Forms determines the edit widget in TableCrafter.

TableCrafter re-fetches this data on each page load by default. If your data source updates infrequently and your site has significant traffic, enable the built-in caching option in the table's Performance tab. This stores the fetched data for a configurable number of minutes and serves it from WordPress transients, reducing API calls to the source and improving page load time for visitors.

How Options Are Loaded?

TableCrafter uses a three-tier fallback system to load dropdown options when a lookup cell enters edit mode.

Tier 1: Cached Options in Page Load

When TableCrafter renders the table, it inspects every editable column. For columns that will render as dropdowns, it embeds the option list as a JSON object in the page's configuration block. When the user taps a lookup cell, the dropdown options are already in memory, no AJAX call needed. This is the fastest path and works for most GF Select fields with a static list of choices defined in the form builder.

Tier 2: AJAX Fetch from Source Form

If the lookup column is configured to pull dynamic options from another form's entries (e.g., a Drivers form that supplies driver names to a dropdown in a Loads table), the options cannot be embedded at page load time because the source form's entries change. Instead, when the user taps the lookup cell, TableCrafter fires an AJAX request to fetch the current option list from the source form. A brief "Loading..." message appears while the request completes. This should resolve in under one second on a local-hosted WordPress site. Network latency on shared hosting may cause a 1 to 2 second delay.

Tier 3: Static Fallback List

If both Tier 1 and Tier 2 fail to return options (source form not found, empty form, API error), TableCrafter falls back to any static options list you've configured in the column settings under Fallback Options. Enter a comma-separated list of values there. These display as the dropdown options when dynamic loading fails. This prevents the "Loading options..." permanent spinner by always providing a usable state.

How Do I Configure a Lookup Column?

To configure a column as a dynamic lookup sourced from another form:

The configuration you set here applies to every visitor who loads a page containing this table, regardless of whether they are logged in. Role-specific overrides for columns and rows are a separate layer and do not replace these global display settings. Apply global settings first, then add role restrictions as needed for tables that serve multiple user types.

1. In the table builder, click the column that should be a lookup field.
2. Enable Allow Inline Edit.
3. In the Edit Widget dropdown, select Lookup Dropdown.
4. Under Lookup Source, choose Gravity Forms Entry.
5. In Source Form, select the GF form whose entries will supply the option list.
6. In Display Field, select which field from the source form to use as the visible option label (e.g., the Driver Name field).
7. In Value Field, select which field to use as the stored option value (e.g., Driver ID, or the same name field if names are the stored value).
8. Optionally add a comma-separated Fallback Options list.
9. Save the table.

How the Dropdown Behaves Inside the Cell?

When a lookup cell enters edit mode, the cell's static text is replaced by a styled dropdown widget. On desktop, this is a custom-rendered dropdown (not the browser's native <select>) that matches the table's visual design. The dropdown opens downward from the cell; if the cell is near the bottom of the visible area, it opens upward instead to stay in the viewport.

The user can navigate options with the arrow keys and select with Enter, or click an option. After selection, the cell immediately shows the new value and the AJAX save fires. The dropdown closes automatically after a selection.

On mobile, the native <select> element is used for better touch handling, as described in the mobile editing guide.

This step completes the connection between your data source and the TableCrafter table engine. Once saved, the plugin caches the connection credentials in the WordPress options table and uses them on every subsequent page load. If you update the source configuration later — for example, rotating an API key or changing a sheet URL — return to this step, enter the new value, and save again. The table updates immediately on next load without any shortcode changes.

How Does User Lookup Fields Work?

A special case of lookup fields is a column that pulls options from the WordPress user list rather than a GF form. TableCrafter supports this through the Lookup Source: WordPress Users option in the column settings. Configure it by:

1. Setting Lookup Source to WordPress Users
2. Optionally filtering by role (e.g., only show users with the driver role in the dropdown)
3. Choosing whether to store the user's display name or their user ID as the entry value

This is the correct approach for an "Assigned To" column that should let users select from a list of team members. The WordPress user list updates automatically as you add or remove users, no static options list to maintain.

If this step produces unexpected output, check the source data directly in the connected system. TableCrafter passes data through without modification — if a cell displays an unexpected value, the source record contains that value. Use the TableCrafter debug log (Settings > Advanced > Debug Mode) to trace the exact query sent to the source and the raw response received, which narrows the diagnosis to either a source-side or rendering-side issue.

What Is Troubleshooting: Options Not Loading?

Dropdown Shows "Loading options..." Permanently

Open browser DevTools, go to the Network tab, and trigger the dropdown by clicking the lookup cell. Look for the AJAX request to admin-ajax.php with action gt_get_lookup_options. Check the response:

• 200 with empty options array: The source form exists but has no entries, or your entry filters are excluding all entries. Add entries to the source form or remove the filter.
• 200 with error key: The source form ID in your column config doesn't match any existing form. Re-open the column settings and re-select the source form.
• 403 or 401: The current user doesn't have permission to read entries from the source form. Check that your table's View Roles include the current user's role.
• 500: PHP error in the AJAX handler. Check wp-content/debug.log.

Dropdown Shows Options But Doesn't Save

If selecting an option doesn't update the cell value, the issue is usually that the Value Field configured in the lookup column doesn't match what the original GF field expects. For example, if the GF field stores a driver name as a string but your lookup Value Field is set to a numeric ID, the save will succeed (the AJAX call completes) but GF may store an unexpected value. Re-check the Value Field configuration and confirm it matches the GF field's storage format.

Options Show Stale Data

If Tier 1 caching is active (static options embedded at page load) and the source form's choices have been updated since the page was cached, users will see old options. This happens when your page caching plugin caches the table's HTML including the embedded options JSON. Exclude the page from HTML caching or configure TableCrafter to always use Tier 2 AJAX loading for this column by toggling Always Fetch Options Dynamically in the column settings.

What Are the Next Steps?

Lookup fields are one of the most valuable inline editing components because they enforce controlled vocabularies, users pick from valid options instead of typing free text. Combine lookup fields with required validation (so a lookup cell cannot be cleared) and role restrictions (so only authorized roles can change a dropdown value) for maximum data integrity on your most critical categorical fields.

When testing this feature, verify the result while logged in as a user with the target role, not as an admin. WordPress administrators see all rows and columns by default, which means admin accounts will not reflect role-restricted configurations during testing.

The shortcode accepts all column and filter settings defined in the table builder as defaults, but you can override individual parameters inline. For example, `[tablecrafter id="1" per_page="25"]` overrides the default rows-per-page setting for this specific embed without changing the saved table configuration. This lets you reuse one table definition across multiple pages with different display requirements.