Yes. Breezing Forms stores fields from all pages on a single record row. The dashboard exposes any field as a chart dimension regardless of which page it lives on. Multi-page complexity disappears at the reporting layer.

Conditional fields appear in the dimension list. Records where the branch did not fire simply do not contribute to that group, so the charts stay predictable. A filter chip can scope every card to records where a specific branch fired or did not fire.

Yes when Breezing's payment add-on writes gateway and amount data to the record. Group by status, filter to paid, sum amount, and the dashboard becomes a finance-reporting surface over the same multi-page form data.

No. SleekView Charts is read-only over the bf_records table. The plugin's submission flow, email notifications, and any payment-add-on processing continue exactly as before.

If Breezing's auto-save or partial-submit feature writes a draft row, yes. Filter to draft or incomplete status and the cards surface the abandoned cohort. Useful for diagnosing where users drop off in long forms.

Queries hit indexed columns on bf_records (id, form_id, status, submitted) directly. Aggregations on conditional or per-page fields read from the record payload, which is inexpensive on tens of thousands of rows.

Yes. Pick a list of form IDs and the cards aggregate across them with a form filter chip to scope when needed. Both cross-form rollup and single-form deep dive are supported.

It counts records with non-empty upload fields, which is useful for application-style forms where attachment rate matters. The files themselves stay in the table view rather than appearing in chart aggregations.