SleekView Charts for Formidable Forms
Group frm_items by form_id, user_id, is_draft, created_at, or any pivoted frm_item_metas key. Count entries, average calculated-field values, and chart submission trends across every form in one view.
♾️ Lifetime License available
Long-format meta as chartable dimensions
Formidable Forms keeps entries in frm_items with per-field values rolled out as long-format rows in frm_item_metas. Form definitions live in frm_forms and field metadata in frm_fields. The default admin lists entries per form and offers limited reporting through Formidable Views, but a real cross-form chart dashboard isn't part of the admin.
SleekView Charts reads frm_items directly, joins frm_forms for readable form names, and pivots frm_item_metas at query time so per-field values become chartable dimensions. Group by form_id, is_draft, user_id, created_at, or any meta key. Sum, count, or average calculated-field values without dropping into PHP.
Repeater fields complicate aggregates: parent entries and child rows both live in frm_items linked by parent_item_id. SleekView lets the view filter on whether children are included so an entry-count chart doesn't double-count line items on an order form.
Workflow
From frm_item_metas to chartable cards
Read frm_items + frm_forms
frm_items as the dataset. SleekView joins frm_forms for readable form names so the form group-by uses titles instead of IDs.
Pivot meta into dimensions
meta_key from frm_item_metas as a group-by option. SleekView pivots at query time using frm_fields for the label so charts use the field's human name.
Add aggregates
frm_item_metas so the chart reads them as numbers without recalculating.
Filter and save
form_id, is_draft, user_id, and date range into one saved view. Cards on the view scope to the same filters.
Sample dashboard
Charts you can build from Formidable data
Total entries
Count
Draft mix
Count
group by is_draft
Entries by form
Count
group by form_id
Entries over time
Count
group by created_at
Comparison
Default Formidable reporting vs SleekView Charts
Default Formidable reports
- Default reports cover graphs per field per form, not cross-form
-
Pivoting
frm_item_metasfor chartable dimensions isn't surfaced in the admin - Cross-form entry counts and trends aren't a built-in dashboard
- Repeater entries inflate aggregates unless filtered out manually
- Per-user activity charts aren't part of the reports screen
SleekView Charts
-
Number, Pie, Bar, and Area cards on
frm_items -
Group by
form_id,is_draft,user_id, or pivoted meta keys - Count entries, sum calculated fields, average numeric values
- Repeater-aware filters to avoid double counting children
- Shared dataset with Table, Kanban, and Feedback views
Features
What SleekView Charts gives you for Formidable Forms
Pivoted meta as dimensions
Pick any meta_key as a chart group-by. SleekView pivots frm_item_metas at query time using frm_fields for the readable label, so charts use the field's human name.
Calculated fields as numbers
Calculated fields persist their result in frm_item_metas, so charts can sum or average them directly. Total revenue from a pricing calculator field, or average score across a quiz, becomes a single card.
Repeater-aware counts
Filter charts to parent entries only, child rows only, or both. Order-form charts count one entry per order, not per line item; line-item charts count children directly.
Audience
Who builds Formidable charts dashboards with SleekView
Form admins
Submission counts per form, draft versus published mix, and dormant-form detection. Audit the whole installation in one saved view rather than form-by-form.
Calculator-form operators
Sum and average calculated-field values across submissions. Pricing-quote forms, ROI calculators, and quiz scores produce real numbers that belong on a chart.
Membership and community managers
Group by user_id to chart per-user submission counts, identify power users, or spot accounts with unusual activity patterns.
The bigger picture
Why long-format meta needs a pivot-aware chart layer
Formidable's flexibility comes from the long-format frm_item_metas design: any field structure fits without schema changes. That flexibility makes the database scale and makes per-field values invisible to aggregate queries until you pivot. Formidable's reports tab handles single-field-single-form graphs, but cross-form trends, per-user activity charts, and calculated-field sums need a real dashboard surface.
Repeater fields complicate aggregates further: parent entries and child rows share the table linked by parent_item_id, so naive counts double-count line items on an order form. SleekView Charts pivots meta on demand, lets the view filter on parent versus child rows, and exposes every entry dimension as a group-by option. Same data, same hooks, dashboards that finally match how teams use the plugin.
Questions
Common questions about SleekView Charts for Formidable Forms
No. Views renders entries on the front-end for visitors; the reports tab handles per-field-per-form graphs. SleekView Charts is an admin-side cross-form dashboard layer on the same data. Teams typically run all three: Views for visitor pages, reports for quick per-form graphs, SleekView Charts for cross-form dashboards.
Yes. Calculated fields store their persisted value in frm_item_metas like any other field, so charts can sum, average, or min-max them. The chart reads the stored value rather than recalculating, which is usually what you want for historical dashboards.
Each repeater iteration is a child entry linked via parent_item_id. Charts let the view choose to include parents only (typical for entry-count dashboards), children only (for line-item-level analysis like order details), or both. Default is parents only to avoid double counting.
Yes. user_id is a column on frm_items and a valid group-by. SleekView can join users to show display names instead of numeric IDs on the chart axis.
No, charts are read-only. Aggregations run as SELECT ... GROUP BY queries with no writes, so no frm_ hooks fire. Edits to the underlying entries from the Table tab use Formidable's CRUD APIs and fire hooks as expected.
Yes. frm_forms provides readable form names for the form group-by. frm_fields provides labels for pivoted meta keys so charts use the field's human name rather than the underlying meta key.
Aggregations use indexed columns on frm_items (form_id, created_at, user_id). Pivoted meta charts add a join cost; scope by date range to keep query plans tight. Most installations stay responsive in the hundreds of thousands of entries.
Each card exports its aggregated rows as CSV with the group-by labels and aggregate values. Useful for handing operations or finance the underlying numbers behind a chart, or archiving the dashboard state at the end of a reporting period.
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 checkout