FormCraft does not ship a strong reporting layer beyond per-form lists. SleekView Charts reads the same formcraft_3_submissions table and renders the picture as a configurable dashboard with cards, filters, and saved views. The two are complementary rather than overlapping.

Per-field values in FormCraft are stored as a serialised blob on the submission row. SleekView reads the row directly for the count, date, and form charts. For charts on specific field values, SleekView can extract individual keys from the serialised blob using its query layer, though indexed metadata columns are always faster to chart against.

Where FormCraft writes the value to an indexed column or to a separate table, charts filter on it directly. For values inside the serialised blob, filter expressions can match the value but at the cost of a full table scan, so scope by date range to keep performance reasonable.

FormCraft 2 used a different table name and storage layout. SleekView can be pointed at FormCraft 2's tables, but the field-extraction logic differs because the older schema serialises differently. Most current sites run FormCraft 3, where the patterns described here apply directly.

Live. SleekView Charts queries the FormCraft tables directly, so a card refresh reflects submissions up to the moment of the request. There is no separate sync that can fall behind.

Yes. SleekView views are gated by WordPress capability, so a client or stakeholder with the right cap can read the dashboard without admin rights. Frontend embedding works too, useful for sharing trends with people outside WP Admin.

No. Chart queries hit indexed columns on form_id and submission_date. Aggregations are bounded by the date range or filter on each card, so even sites with hundreds of thousands of submissions return chart numbers in well under a second when scoped to a reasonable window.

Where FormCraft writes payment metadata to its own table or to a meta column, SleekView reads it as another data source and can chart revenue and status alongside submission volume. The exact column names depend on the add-on version, but the join pattern is the same as the core submission read.