No, the two serve different audiences. Formidable Views renders entries to site visitors on the front end. SleekView Charts is an admin-side reporting surface for the same data. Most teams run both, Views for visitor pages and SleekView Charts for the team dashboard.

Yes. Repeater children are linked by parent_item_id with their own frm_item_metas rows. SleekView flattens them into parent rows when you want one entry per result, or exposes them as their own dataset when the repeater itself is the data you care about.

Yes. Calculated fields store their result in frm_item_metas like any other field, so they pivot into a column that any chart card can group or aggregate on.

Charts read the standard frm_items and frm_item_metas tables, both of which exist in the free Formidable Forms plugin. Pro features like repeaters and calculated fields appear when present, and the dashboard works either way.

Edits made from the linked table view route through Formidable's CRUD APIs where available, so frm_after_update_entry and related actions fire normally. The chart surface itself is read-only and only reflects what the underlying data already says.

Yes. is_draft is a column on frm_items, so a chart card can filter to drafts only, exclude them, or compare draft versus published in a single Pie or Bar.

Aggregations run against indexed columns on frm_items and a single pivot pass over frm_item_metas. On installs with a few hundred thousand entries the cards refresh in well under a second, and dashboards cache by saved view.

Yes. Any filtered slice behind a chart card exports as CSV with the same columns the table view would show. Useful for board reports or for handing the data to an external BI tool.