SleekView for Quform Pro: entries as customizable tables
Reads from quform_entry and pivots quform_entry_data into proper columns. Cross-form filters, saved views, and bulk inline edits inside WP Admin.
♾️ Lifetime License available
Entries as a real table, not a per-form CodeIgniter screen
Quform Pro stores submissions in quform_entry with field values written to quform_entry_data in long format (one row per field per entry). The default admin lists entries per form with filtering inside that form, and field values are visible after opening each entry. Cross-form audits and bulk inline edits aren't first-class moves.
SleekView reads both tables and pivots quform_entry_data into named columns sourced from the form's field configuration in quform_form. Add form_id as a column and you get a unified inbox: contact entries, application forms, and order forms in one workspace. Filter by date_added, status, is_read, or any field meta in combination, then save the result as a named view.
Edits route through Quform's entry update path where supported, with direct writes to quform_entry_data as a fallback. Conflict detection on date_updated guards against concurrent edits, and writes respect Quform's sanitisation hooks.
Workflow
From quform_entry_data long-format to a real table
Point at quform_entry
quform_form to discover available forms and their field configurations, so the column chooser knows your real schema.
Pivot entry data into columns
quform_entry_data as a typed column. The pivot runs at query time so new fields appear immediately.
Combine filters
form_id, date_added, status, is_read, and field-level filters in one saved view. Scope to roles so each team sees its own slice.
Edit inline or in bulk
Sample columns
A typical Quform Pro entry table
quform_entry_data into proper columns labelled by quform_form's field configuration.
wp_quform_entry + wp_quform_entry_data + wp_quform_form
| Entry | Form | Added | Amount | Status | |
|---|---|---|---|---|---|
| #732 | Contact | Apr 24 | alex@studio.co | Unread | |
| #731 | Application | Apr 24 | ria@design.io | Reviewed | |
| #730 | Order | Apr 23 | tom@hello.dev | $64.00 | Paid |
| #729 | Order | Apr 23 | mia@brew.coop | $64.00 | Failed |
Comparison
Default Quform Pro admin vs SleekView
Default Quform Pro admin
- Entries are scoped to one form at a time in the default screen
-
quform_entry_datastays in long format until rendered per-entry -
Bulk-toggling
is_readorstatusacross forms isn't first-class - Cross-form audits need custom queries or CSV exports
- Filtering on field-level values isn't built into the stock admin
SleekView
-
Cross-form entry table with
form_idas a sortable column -
Pivot
quform_entry_datainto typed columns usingquform_formfield labels -
Filter by
date_added,status,is_read, and any field together - Inline-edit field values and statuses without per-row clicks
- Save filtered views per role and per workflow
Features
What SleekView gives you for Quform Pro
Pivot entry data into columns
Quform stores each field value as a row in quform_entry_data. SleekView pivots them at query time using the form's field configuration in quform_form, so each entry is one row with named columns.
Combine filters across forms
Mix form_id, date_added, status, is_read, and field-level filters in one saved view. Cross-form inboxes and per-form triage share the same engine.
Inline and bulk edit
Update field values, flip status, mark entries read across many rows. Quform's entry update path handles validation; direct writes cover field types it doesn't fully expose with conflict detection.
Audience
Who uses SleekView for Quform Pro
Support and sales
Inbound entries across every form in one table, filtered to unread plus last seven days. Star priority items, bulk-mark resolved when the thread closes.
Finance
Paid order entries by date range with payment-amount as a sortable column. Export the filtered set for reconciliation against gateway exports.
Form admins
Audit which forms still receive entries, clean up old ones by form_id, and manage is_read across the whole site in a single pass.
The bigger picture
Why Quform entries need a real table view
Quform Pro has been a steady choice for WordPress sites that need a powerful form builder with a clean per-form admin. The long-format storage in quform_entry_data makes the schema flexible (any field structure fits without migrations) but the same design forces the admin to be per-form because cross-form pivots aren't free. Teams running Quform across many forms (contact, applications, payment forms, support intake) hit the same operational walls every forms plugin does: no cross-form inbox, no bulk status edits, no field-level filters across the site.
SleekView treats quform_entry as a queryable source where pivots are cheap and filters compose, which means support, finance, and form admins each get a workspace tuned to their workflow without writing SQL.
Questions
Common questions about SleekView for Quform Pro
Yes. Any add-on storing data in quform_entry_data (payment add-ons, integrations, custom fields) is automatically visible because its data lives as field keys on the entry. The pivot picks them up without per-add-on configuration.
Yes. SleekView writes through Quform's entry update path for supported field types (text, email, number, select, checkbox, date), falling back to direct writes against quform_entry_data with conflict detection on date_updated.
SleekView reads the field configuration from quform_form for the entries you're viewing and joins quform_entry_data by entry_id. Each field becomes an addable column at query time, so newly added form fields appear immediately.
Yes. Add form_id as a column and filter to a subset of forms or leave it open. Only field keys shared across selected forms become broadly useful columns; SleekView labels each field with its form.
Yes. Both is_read and status live on quform_entry and SleekView exposes them as inline-editable columns. Bulk-toggle across many entries is supported without per-row clicks.
Upload-field values store the file URL or attachment ID in quform_entry_data. SleekView renders these as filename cells linked to the file or media library; "has attachment" works as a one-click filter.
Quform's notification and integration hooks are usually configured to run on entry creation. Inline updates fire Quform's update hooks where present, but most notifications won't re-trigger on update. Test one row before bulk-applying.
The join between quform_entry and quform_entry_data is paginated server-side with filters applied first. Scope a view by date range or form_id to keep the column-chooser inspection responsive on large tables.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Woocommerce Lottery
- Sprout Invoices
- Woocommerce Conditional Shipping And Payments
- Woocommerce Shipping Canada Post
- Woocommerce Recently Viewed
- Woocommerce Quick Order
- Woocommerce Moneris
- Woocommerce Cod Fee
- Woocommerce Tiktok Pixel
- Woocommerce Prices By User Role
- Wp Ecommerce
- Woocommerce Iyzico
- Woocommerce Glsship
- Woocommerce Name Your Price
- Woocommerce Hermes Shipping